rameters to be
> preserved. Hmm, I wonder if the original value would still be in the
> arguments array???
>
> -Original Message-
> From: prototype-scriptaculous@googlegroups.com
>
> [mailto:prototype-scriptacul...@googlegroups.com] On Behalf Of Blaine
> Sent: T
com] On Behalf Of Blaine
> Sent: Thursday, September 09, 2010 1:29 PM
> To: Prototype & script.aculo.us
> Subject: [Proto-Scripty] Re: element is null suggestion
>
> I think the way it is is intuitive to JavaScript developers who know
> Document.getElementById(). If the element may
ehalf Of Blaine
Sent: Thursday, September 09, 2010 1:29 PM
To: Prototype & script.aculo.us
Subject: [Proto-Scripty] Re: element is null suggestion
I think the way it is is intuitive to JavaScript developers who know
Document.getElementById(). If the element may return null, then check
for null
I think the way it is is intuitive to JavaScript developers who know
Document.getElementById(). If the element may return null, then check
for null dammit ;-) ... just as if you were coding directly with w3c
API.
WRT console logging, there are tons of places where console logging
would be useful
Could you set this up on http://jsbin.com/?
On Tue, Jun 16, 2009 at 2:06 PM, adamski wrote:
>
> I'm having some trouble getting a Draggable to dorp onto a Droppable.
> I get the old "element is null" error from prototype (its trying to
> show an non-existent element).
>
> However, the element
A good night's rest made me see that I did not have an id attribute on
the form element, just a name. My bad. That gets me sometimes when I
am referencing form fields.
By the way, the code is actually velocity, a little-known java
template language. It was part of a project we ended up using a fe
Hi,
> The line:
>
> Event.observe('$formName', 'submit', checkReqFields, false);
>
> is causing...
In the code you quoted, that line doesn't exist; this does:
> Event.observe('fm', 'submit', checkReqFields, false);
I assumed at first that you were quoting the end result that went to
the br
