I like the idea of having one handle for those cryptic error codes.
Would onNetworkError be different than onException ( does the
onException get called as well??)
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hi Ken,
I didn't push the getStatus method further than that because there are
some issues with the file protocol in Safari (status is always equal
to 0 in that case if I remember well).
Proper support for the file protocol is something I'd like to have for
1.6 final.
It implies rewritting
Thanks Mislav,
In prep for my reply I was looking through the 1.6_rc0 release and I
have to give you guys a HUGE hand on the event firing using a real
event object.
Very very cool stuff...
I am trying to think of the easiest way to explain the problem and the
solution.
Take for example my old
But you could prevent it if you managed them in an array... as I
discussed.
As well as have the rest of the benefits your current implementation
lacks...
The only core difference between my implementation and the current 1.6
is that I send mine to a js array and 1.6 still relies on the browser
In my code this was an issue because I had a forl oop iterating over
the DOMContentLoaded observers and,
I had a case where the loop would be half through and the window
onload would fire,
calling code that hadent yet been inited in the DOMContentLoaded
observers.
Becuase 1.6 uses a real event
jdalton wrote:
I like the idea of having one handle for those cryptic error codes.
Would onNetworkError be different than onException ( does the
onException get called as well??)
In my current implementation, a network error triggers onNetworkError,
onLoaded, onComplete, then onFailure.
Quick question: why does Element.wrap return the wrapped element
instead of the wrapper?
I've yet to find somewhere where I use wrap that I don't do .wrap(...).up()
Is it just me?
-Nicolas
--~--~-~--~~~---~--~~
You received this message because you are
On 9/7/07, jdalton [EMAIL PROTECTED] wrote:
Before the window onload event is fired I check to see if the
DOMContentLoaded has been notified or if they equal each other (if the
browser dosent support any form of DOMContentLoaded emulation I have
it fallback on the window onload event)
I've corrected this, thanks for the heads-up!
Best,
thomas
Am 07.09.2007 um 19:59 schrieb Les:
There is nothing wrong with out code, but with your JS compression
software.
I found this cute typo :)
http://www.prototypejs.org/contribute
On 9/7/07, Nicolás Sanguinetti [EMAIL PROTECTED] wrote:
Quick question: why does Element.wrap return the wrapped element
instead of the wrapper?
Consistency. Element.Mehods methods always return self to allow for
chaining.
I've yet to find somewhere where I use wrap that I don't do
10 matches
Mail list logo
