[Prototype-core] Re: Predefined custom events handled as 'dataavailable' (1.6.0_rc0)

2007-08-17 Thread jdalton

Also is there any validity in the concern that without proper checks
the window.onload trigger could happen in the middle of executing the
contentloaded observers (esp. in IE when you are emulating a
contentloaded event)?

Do you have a way to ensure proper first in first out order or event
observers executing?

(I believe YUI does my having one true observer of an event acting as
a proxy for all other observers, storing them in an array and
iterating over the array when its triggered)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Predefined custom events handled as 'dataavailable' (1.6.0_rc0)

2007-08-17 Thread Andrew Dupont

This is probably the most glaring flaw in RC0: any event types that
are not part of the DOM L2 Events spec, but are nonetheless honored by
one or more browsers, are handled incorrectly by Prototype as custom
events.

We've got to figure out a way around this, even if it means we create
a whitelist of all known event types to work in modern browsers. The
convenience of handling both custom and standard events with the same
API shouldn't make it harder to (for instance) skate on the bleeding
edge of Web Forms 2.

I'll make sure we figure this out before RC1.

Cheers,
Andrew

On Aug 17, 8:12 am, Wiktor Ihárosi [EMAIL PROTECTED] wrote:
 The new prototype is under heavy test and I find another intresting
 bug...

 The modified observe method try to get the name of the passed
 eventName by getDOMEventName but this is limited to the well-known
 events. Any unknown event will handled as 'dataavailable'.

 This cause problems if you use predefined events, for example using
 fantastic repetitionmodel (webforms2 now) implementation by Weston
 Ruter which implements new Web Forms 2 events. But the problem is same
 if you use Opera9, it has native support for these events.

 Here is an example 
 page:http://devidens.hu/spacergif/2007/08/17/predefined-custom-events-hand...

 Please check in Opera, and click on the Add Row button. You should see
 two alerts, but you will only one.

 Unfortunately I am not good at the event model, so I don't know what
 is the reason of the 'dataavailable', but my dirty hack is to return
 eventName is condition fail. It works for me. :)

 if (!Event.DOMEvents.include(eventName)) return eventName;
 instead of
 if (!Event.DOMEvents.include(eventName)) return dataavailable;


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---