Side navigation
#4261 closed bug (fixed)
Opened February 26, 2009 08:07PM UTC
Closed February 04, 2010 05:32AM UTC
.click method - behavior varies across browsers
Reported by: | peterd | Owned by: | brandon |
---|---|---|---|
Priority: | minor | Milestone: | 1.4.2 |
Component: | event | Version: | 1.4.1 |
Keywords: | click method | Cc: | |
Blocked by: | Blocking: |
Description
If a new event handler is added to an object via the .click method within a click event, the behavior varies across browsers.
In IE7, the new behavior is added *and executed*. In Firefox, it is added but not executed until the next click event.
See http://net35.ccs.neu.edu/home/peterd/BrowserDifferences/BehaviorAddedToClick.htm
for an example
Attachments (0)
Change History (3)
Changed February 27, 2009 02:21AM UTC by comment:1
Changed August 07, 2009 05:15PM UTC by comment:2
component: | unfilled → event |
---|---|
owner: | → brandon |
Changed February 04, 2010 05:32AM UTC by comment:3
milestone: | 1.4 → 1.4.2 |
---|---|
resolution: | → fixed |
status: | new → closed |
version: | 1.3.2 → 1.4.1 |
To summarize,
The page is adding a second click handler for #Button1 while in the middle of a click event being dispatched to #Button1. I do see the difference in behavior that you describe. What is the *expected* behavior for a case like this? It seems like either way could be correct.