Opened 10 years ago
Closed 10 years ago
#13660 closed bug (invalid)
ie9 lose focus on focusin event
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.9.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
i am using jquery mobile 1.3 with jquery 1.9.1 and when i click on a selectmenu with option nativeMenu = false, IE9 lose focus and go backward.
I fixed the problem by removing the focusin event added for firefox 17+ (ln 1443)
// Support: IE<9 (lack submit/change bubble), Firefox 17+ (lack focusin event) // Beware of CSP restrictions (https://developer.mozilla.org/en/Security/CSP), test/csp.php for ( i in { submit: true, change: true, focusin: true }) {
become
for ( i in { submit: true, change: true }) {
Change History (5)
comment:1 Changed 10 years ago by
Owner: | set to [email protected]… |
---|---|
Status: | new → pending |
comment:2 Changed 10 years ago by
Status: | pending → new |
---|
sorry for the delay http://jsfiddle.net/Q7Fbd/3/embedded/result/
I only have the problem when only one tab is open, and when I click at least 2 times on the select.
I don't know why but the HTML generated by jsfiddle is not visible on IE9. I must set the compatibility mode (but have the problem without the compatibility mode when i don't pass through jsfiddle):
- Navigation Mode: IE9 Compatibility View
- Document Mode: IE7 Standards
comment:3 Changed 10 years ago by
Status: | new → pending |
---|
Sorry, this is too much code to debug. Can you reduce it to just the jQuery core script?
comment:4 Changed 10 years ago by
i'm sorry i didn't have the time to create a case in order to reproduce the problem without jquery mobile.
I will try in the following days
comment:5 Changed 10 years ago by
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!
Can you provide a test case on jsfiddle.net? That would help us determine where the problem lies.