Hi,
You get that error when you try to use a Prototype or script.aculo.us
method on a DOM element that you haven't extended, more here:
http://proto-scripty.wikidot.com/prototype:tip-object-doesn-t-support-this-property-or-method
HTH,
--
T.J. Crowder
Independent Software Consultant
tj / crowder s
Hi,
i'm using protoaculous.1.8.3.min.js (great job!).
I included this script with
It work well with chrome but i get errors with I.E 8 :
- Object doesn't support this property or method | Line 1 |
character80623
and only almost, in addition :
- Object doesn't support this property or method | L
Hi,
On Jun 21, 9:58 pm, Jason 'XenoPhage' Frisvold
wrote:
[snip]
> What about a non-HTTP error? What if, for
> instance, myId was invalid? What is the proper way to pass that
> information back to the ajax application? Is it ok to use a custom 4xx
> error? Or should I be using JSON or XML to
"Element.update('code_text', ' I'm using Element.update inline to modify the contents of a textarea.
> If the updated text doesn't contain any html it works fine. For
> example the following code works and updates the text area with the
> simple text of small, medium, or large.
>
> Small
> Medium
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I have a question, perhaps a bit newbie-ish, but I think it's important
nonetheless. What is the proper way to handle errors reported by
back-end processes via Ajax? For instance, let's take a very simple
Ajax.Request call like this
Hi,
I have just remplaced protoaculous.1.8.3.min.js by protoaculous.
1.8.2.min.js and, it's fantastic, everything work (modalbox,
lightbox...). Is there errors in your protoaculous.1.8.2.min.js
perhaps?
Thanks a lot
On 22 juin, 08:37, "T.J. Crowder" wrote:
> Hi,
>
> You get that error when you
I don't know...
It's on this page : http://tutosnumeriques.olympe-network.com/
Can you see the source to say me what it's wrong?
Thanks!
On 22 juin, 08:37, "T.J. Crowder" wrote:
> Hi,
>
> You get that error when you try to use a Prototype or script.aculo.us
> method on a DOM element that you h
Oh thank god. i thought i was being incredibly dense using a solution
like that. But having seen no other way to determine the procedural
path to take when the server responds (barring a transport error),
that seems the most effective way to follow one route for successes
and another for failures/e