-
Notifications
You must be signed in to change notification settings - Fork 20.6k
Firefox throws error in Sizzle due to XHTML violation in feature check #1969
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
Comments
The change was in jquery/sizzle@aca006d and since |
Fortunately we have tests for reported support tests results: Lines 54 to 226 in 76df9e4
so if any result changed, we'd detect that. That is, unless a problem exists in XHTML mode only which we (cough) currently don't test. |
This will be fixed when we merge the latest sizzle. |
(jquery is updated to 1.11.1 instead of 1.11.3 because the fix for jquery/jquery#1969 bug which was introduced in 1.11.2 isn't out yet)
I interpret the For the next person to google this, I was using jqGrid when I noticed the "not well-formed" in the console after an upgrade to jQuery 2.1.4. Not to be confused with other threads of people using jqGrid with actual malformed XML. (Coincidentally(?), the OP @herbalite is a contributor to free-jqgrid). Also for the next person to google this, issue #2196 has a link to a fiddle that simply reproduces the problem. I also verifyied that jquery/sizzle@50ebe1a fixed the problem for me too, by applying that patch manually to 2.1.4. |
I'm pretty sure this will be in the 1.12.0/2.2.0 release that we plan to do later this month, since it was in the Sizzle update. @gibson042 can you confirm that's the case and update the milestone if so? |
Confirmed. |
Hi, I arrived at this issue because I'm getting the same error in Chrome v66 on a page that uses jQuery 2.2.4 and the WYMeditor plugin. There's a way to reproduce this error almost every time in a very specific case: using a mutation observer that contains I've uploaded a test page here: |
@thdoan If you can reproduce that using http://code.jquery.com/jquery-git.js then report a new issue. Otherwise it's been fixed in the past and you should upgrade. |
WYMeditor doesn't support jQuery 3.x, but thanks I've managed to avoid this rare scenario for the time being. |
Under circumstances, that I have not yet been able to reproduce as a simple test case Firefox 34 throws a system error.
In Firebug I get the following error output. The invisible char in the output below (after select id="sizzle1419480912644-
invisible char
" is in fact a line feed shown by Firebug.malformed input
From the popup over the error code my guestimate it is an issue of mix between XHTML and HTML tags.
As the in the popup over the error line the link reads
So there's the switch from xhtml to html
The source code for 2.1.3 for this issue is found on line 1176 and has the following code
That code changed from 2.1.1. to 2.1.3 and the issue it seems to be that -\f is being interpreted by Firefox as a line feed and trips up Firefox. With other browsers I don't see this issue. The issue is also present in the minified version.
Except for the showing in the debugger however the page appears to work fine. So for me it's not a show stopper, but a step backwards from 2.1.1
The text was updated successfully, but these errors were encountered: