Side navigation
#11148 closed bug (invalid)
Opened January 10, 2012 02:36PM UTC
Closed February 13, 2012 08:16AM UTC
Focus event doesn't fire, but focusin fires twice
| Reported by: | dmethvin | Owned by: | dmethvin |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | event | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Reported by @DonTAbrams
Attachments (0)
Change History (5)
Changed January 10, 2012 02:36PM UTC by comment:1
| component: | unfiled → event |
|---|---|
| milestone: | None → 1.7.2 |
| priority: | undecided → high |
Changed January 10, 2012 02:37PM UTC by comment:2
| owner: | → dmethvin |
|---|---|
| status: | new → assigned |
Changed January 11, 2012 02:31PM UTC by comment:3
The fiddle affected by the regression is this: http://jsfiddle.net/donabrams/MLnRg/1/
Changed January 29, 2012 05:27PM UTC by comment:4
| milestone: | 1.7.2 |
|---|---|
| status: | assigned → pending |
Don, can you refresh me on where/why this was not working correctly? I am not seeing a problem. If you could create a simple test case that didn't include the whole plugin that would help.
It's possible that focusin firing twice is correct. If a focus event was fired below the element handling the event, it will be bubbled as a focusin and must be attached as such if it's a bound (vs delegated) event.
Changed February 13, 2012 08:16AM UTC by comment:5
| resolution: | → invalid |
|---|---|
| status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!