-
Notifications
You must be signed in to change notification settings - Fork 940
Selector: Make empty attribute selectors work in IE 11/Edge again #461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
+51 bytes |
|
It looks like the workaround makes Sizzle tests pass in IE 11 & Edge 16-18 but it still fails in Edge 15... I don’t think they’d change the behavior around it somehow & then back so I worry about stability of this workaround. |
|
I submitted #462 to update tested browsers but also add Edge 15 & 16 to the mix so that issues like the one described above are caught more often. |
11f8395 to
4d71b18
Compare
|
PR updated. |
|
|
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Fixes jquery/jquery#4435
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty name attribute selector (`[name=""]`). Detect that & fall back to Sizzle traversal. Interestingly, IE 10 & older don't seem to have the issue. Ref jquerygh-4435 Ref jquerygh-4510 Ref jquery/sizzle#461
qSA in IE 11/Edge often (but not always) don't find elements with an empty
name attribute selector (
[name=""]).Assigning a temporary name attribute tothe document root (& removing it afterwards) seems to resolve the issue.
EDIT: Detect that & fall back to Sizzle traversal.
Interestingly, IE 10 & older don't seem to have the issue.
Fixes jquery/jquery#4435
jQuery version of the PR: jquery/jquery#4510