master
Commits on Mar 30, 2020
-
Build: Remove the version field from the bower.json file
jquery-release only updates the version in the tag so it stays stale on master. Instead, just remove the version from there. Closes gh-469
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Mar 13, 2020
Commits on Mar 2, 2020
-
Release: Make Sizzle work with jquery-release, remove generated files
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Feb 28, 2020
Commits on Oct 21, 2019
-
Selector: Make empty attribute selectors work in IE 11/Edge again
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. Closes gh-461 Fixes jquery/jquery#4435
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits -
Selector: Throw on post-comma invalid selectors in Opera 10-11 again
PR gh-456 introduced a test catching not throwing on badly-escaped identifiers by Firefox 3.6-5. Unfortunately, it was placed just before a test Opera 10-11 fails, making Opera fail quicker and not adding a post-comma invalid selector to rbuggyQSA. This commit fixes the regression & introduces a unit test ensuring the throwing. Unfortunately, the issue is fixed in Opera 11.6 which is the lowest one Sizzle officially supports but I verified the fix manually against Opera 10.6, 11.1 & 11.5. Closes gh-463 Ref gh-456
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits -
Tests: Test for Shadow DOM v1 support
There was a test for Shadow DOM nodes working as root but it was using Shadow DOM v0 that only Chromium implements and which it plans to remove in the future. The test was reworked to rely on Shadow DOM v1. jQuery master already uses the new API in its tests. Closes gh-464
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Oct 15, 2019
-
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Oct 14, 2019
-
Selector: Make selectors with leading combinators use qSA again
An optimization added in #431 skips the temporary IDs for selectors not using child or descendant combinators. For sibling combinators, though, this pushes a selector with a leading combinator to qSA directly which crashes and falls back to a slower Sizzle route. This commit makes selectors with leading combinators not skip the selector rewriting. Note that after jquery/jquery#4454 & #453, all modern browsers other than Edge leverage the :scope pseudo-class, avoiding temporary id attributes. Closes gh-460 Ref gh-431
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Oct 10, 2019
-
Selector: Leverage the :scope pseudo-class where possible
The `:scope` pseudo-class[1] has surprisingly good browser support: Chrome, Firefox & Safari have supported if for a long time; only IE & Edge lack support. This commit leverages this pseudo-class to get rid of the ID hack in most cases. Adding a temporary ID may cause layout thrashing which was reported a few times in [the past. We can't completely eliminate the ID hack in modern browses as sibling selectors require us to change context to the parent and then `:scope` stops applying to what we'd like. But it'd still improve performance in the vast majority of cases. [1] https://developer.mozilla.org/en-US/docs/Web/CSS/:scope Fixes jquery/jquery#4453 Closes gh-453 Ref jquery/jquery#4454 Ref jquery/jquery#4332 Ref gh-405
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Oct 1, 2019
-
Selector: Use shallow document comparisons to avoid IE/Edge cras… (#459)
IE/Edge sometimes crash when comparing documents between frames using the strict equality operator (`===` & `!==`). Funnily enough, shallow comparisons (`==` & `!=`) work without crashing. Fixes jquery/jquery#4441 Closes gh-459 Ref jquery/jquery#4471
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Aug 21, 2019
-
Build: Split iOS tests into two sets to improve reliability
The Karma version currently used by Sizzle often re-runs tests in all browsers from the current browser set if one of them fails. To improve reliability, split iOS into two browser sets similarly to how desktop browsers & Android are split. Closes gh-457
-
Build: Run Karma tests sequentially in separate processes + other imp…
…rovements Sizzle hasn't been able to finish all its unit tests successfully for a long time. This commit attempts to make it work again (at least most of the time). Summary of the changes: 1. A new "karma-tests" task is created; it runs tests in various browser sets but does it sequentially in separate processes to avoid Karma bugs that cause browsers from previous sets to somehow still be waited on during subsequent runs, failing the build. 2. Upgrade tested browsers. 3. Run iOS tests at the end (as it fails more often than other browsers). 4. Use real iOS 10.3 device in Karma. We can't upgrade Karma as the latest version (`4.2.0`) hangs in IE 7 (IE 8 seems to work fine there). Closes gh-455
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Aug 20, 2019
-
Selector: Detect incorrect escape handling by old Firefox
According to: https://www.w3.org/TR/css-syntax-3/#ident-token-diagram the escape doesn't need to be followed by a whitespace only if it's not a hex digit or a newline. However, old Firefox (3.6 - 5 only) doesn't throw if an escaped newline is not followed by a space. Fallback to Sizzle in such cases. Fixes gh-454 Closes gh-456
Commits on Aug 19, 2019
Commits on May 29, 2019
-
Build: Update eslint-config-jquery, fix violations, fix the build task
Newest eslint-config-jquery requires prefixing unused function parameters with and underscore; that has been done. The build Grunt task was also fixed to lint the built Sizzle version only after it's built. Ref gh-442
-
Commits on Apr 9, 2019
Commits on Apr 8, 2019
-
-
-
-
gibson042 committed
Apr 8, 2019 -
Verified
This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.GPG key ID: 4AEE18F83AFDEB23 Learn about signing commits
Commits on Jan 14, 2019
-
-
-
Build: Update tested browsers, fix iOS configuration
Firefox, Chrome, Edge & Opera have been updated. iOS 12.0 stopped working but there's a working 12.1 available so I switched to that one.
-
Commits on Nov 4, 2018
Commits on Nov 1, 2018
Commits on Oct 25, 2018
-
Build: Update package-lock.json
mgol committedOct 25, 2018