Opened 14 years ago
Closed 13 years ago
#4261 closed bug (fixed)
.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
Change History (3)
comment:1 Changed 14 years ago by
comment:2 Changed 13 years ago by
Component: | unfilled → event |
---|---|
Owner: | set to brandon |
comment:3 Changed 13 years ago by
Milestone: | 1.4 → 1.4.2 |
---|---|
Resolution: | → fixed |
Status: | new → closed |
Version: | 1.3.2 → 1.4.1 |
Note: See
TracTickets for help on using
tickets.
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.