Opened 10 years ago
Closed 10 years ago
#12518 closed bug (fixed)
Don't use offsetWidth in jQuery.event.trigger()
Reported by: | dmethvin | Owned by: | fracmak2 |
---|---|---|---|
Priority: | high | Milestone: | 1.9 |
Component: | event | Version: | 1.8.0 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
It's currently used to determine whether it's safe to call .focus() on an element without an error in oldIE. However, it causes a reflow and can be a performance killer. Since a direct display:none check won't catch parent-hidden elements I think we'll need to go back to a try/catch for now, but it can be removed in 2.0.
Change History (3)
comment:1 Changed 10 years ago by
Component: | unfiled → event |
---|---|
Milestone: | None → 1.9 |
Priority: | undecided → high |
Status: | new → open |
comment:2 Changed 10 years ago by
Owner: | set to fracmak2 |
---|---|
Status: | open → assigned |
comment:3 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Fixes #12518, removes an offsetWidth on focus/blur events for an <IE9 bug that caused a performance hit. Closes gh-958