Having lurked here for awhile now, I know you guys are very good with
JavaScript in general. I hope it's not against protocol to ask a
question outside of the Mochikit realm.
I have a small site I'm developing for a client and in working towards
greater accessibility for the sight-impaired,
---
A Runtime Error has occurred.
Do you wish to Debug?
Line: 154
Error: 'sucess' is not defined
---
It's a typo - success and sucess.
You should install Microsoft Script Debugger for IE. It's not firebug,
but it does help a bit.
On 1/30/07, Lee
troels knak-nielsen [EMAIL PROTECTED] writes:
---
A Runtime Error has occurred.
Do you wish to Debug?
Line: 154
Error: 'sucess' is not defined
---
It's a typo - success and sucess.
You should install Microsoft Script Debugger for IE.
Hi,
I do not know to program .js, I know very little, I am learning.
you it could explain me, as I could make to work?
Sorry about my english.
On Jan 29, 4:23 pm, Bob Ippolito [EMAIL PROTECTED] wrote:
If you read the sortable_tables example source, you'll see that it's
looking only for TH
Adriano [EMAIL PROTECTED] writes:
Hi,
I do not know to program .js, I know very little, I am learning.
you it could explain me, as I could make to work?
Sorry about my english.
Hi Adriano!
I really recommend you buy a book (at Livrarias Saraiva, Siciliano, Tempo
Real, etc.) on the
Hi.
I'm currently trying the following. First, I construct my output HTML
via DOM constructors, i.e. DIV(null, A(...), ...). Then, I'd like to
traverse the constructed DOM tree in order to append onchange
attributes to all TEXTAREA and SELECT tags. According to the
documentation, DOM is
On 1/30/07, Karsten Patzwaldt [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi.
I'm currently trying the following. First, I construct my output HTML
via DOM constructors, i.e. DIV(null, A(...), ...). Then, I'd like to
traverse the constructed DOM tree in order to append onchange
attributes
Hi all,
I'm very much a MochiKit newb, and I just sunk several hours into
chasing down why it was that the example code at the top of the DOM
documentation page was working when I used the 1.3.1 release, but wasn't
working when I was using the svn trunk head.
It was because DOM wasn't
On 1/30/07, Robert Buels [EMAIL PROTECTED] wrote:
Hi all,
I'm very much a MochiKit newb, and I just sunk several hours into
chasing down why it was that the example code at the top of the DOM
documentation page was working when I used the 1.3.1 release, but wasn't
working when I was using
Well, no. But that helped writing a workaround:
function nodeMap(f, node)
{
nodeWalk(node,
function(node)
{
var ret = node.childNodes;
var res = f(node);
if (res)
{
On 1/30/07, Karsten Patzwaldt [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Well, no. But that helped writing a workaround:
function nodeMap(f, node)
{
nodeWalk(node,
function(node)
{
var ret = node.childNodes;
var res =
Hello all,
I decided to bravely upgrade to the latest head revision of MochiKit
in my code (svn rev 1256) and discovered the name of one of my windows
seems to change after calling the roundElement API.
For example, the following:
alert(window.name);
roundElement('privacyWarning');
12 matches
Mail list logo