Side navigation
#8701 closed bug (wontfix)
Opened March 29, 2011 09:34PM UTC
Closed March 30, 2011 03:46PM UTC
Last modified May 20, 2011 05:06PM UTC
Native events are not triggered at all (chrome/firefox4)
| Reported by: | bgerrissen@gmail.com | Owned by: | |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.next |
| Component: | event | Version: | 1.5.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Example: http://jsfiddle.net/7suaH/
Tested in chrome/FF4 but I think it always applies.
Tested with older jQuery versions as well.
The following API doc implies native events are triggered (and bubbled):
http://api.jquery.com/trigger/
But appears not to be the case.
Seems like DOM event mechanism is circumvented when triggering events, which is ok if you use just jQuery, but when trying to mashup or when authoring lib agnostic toolkits it becomes problematic to say the least. Would be nice if jQuery would share it's events with other kids ;)
Attachments (0)
Change History (3)
Changed March 29, 2011 09:56PM UTC by comment:1
Changed March 30, 2011 03:46PM UTC by comment:2
| component: | unfiled → event |
|---|---|
| keywords: | → needsdocs |
| resolution: | → wontfix |
| status: | new → closed |
It's pretty difficult to meld two event models like that. For us to use the native model would require changes to jQuery's behavior that would break a lot of code.
Changed May 20, 2011 05:06PM UTC by comment:3
| keywords: | needsdocs |
|---|
Docs currently seem clear:
Any event handlers attached with.bind()or one of its shortcut methods are triggered when the corresponding event occurs. They can be fired manually, however, with the.trigger()method. -- http://api.jquery.com/trigger/
After some further investigation, it seems that when .onclick property is directly set (no shim used), the event does fire, but listeners set by native addEventListener do not catch the event at all.
see: http://jsfiddle.net/7suaH/1/