Opened 4 years ago
Closed 4 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 4 years ago by dmethvin
- Component changed from unfiled to event
- Milestone changed from None to 1.9
- Priority changed from undecided to high
- Status changed from new to open
comment:2 Changed 4 years ago by dmethvin
- Owner set to fracmak2
- Status changed from open to assigned
comment:3 Changed 4 years ago by Merrifield, Jay
- Resolution set to fixed
- Status changed from assigned to 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