Selector:Manipulation: Fix DOM manip within template contents #5159
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The
<template/>elementcontentsproperty is a document fragment that may have anulldocumentElement. In Safari 16 this happens in more cases due to recent spec changes - in particular, even if that document fragment is explicitly adopted into an outer document. We're testing both of those cases now.The crash used to happen in
jQuery.containswhich is an alias forSizzle.containsin jQuery 3.x.The Sizzle fix is at jquery/sizzle#490. This PR pulls the new Sizzle version into jQuery's
3.x-stablebranch and backports one test from gh-5158.Fixes gh-5147
Ref jquery/sizzle/pull/490
Ref gh-5158
Checklist
If needed, a docs issue/PR was created at https://github.com/jquery/api.jquery.com