Conversation
🦋 Changeset detectedLatest commit: b5a9d0c The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
CodSpeed Performance ReportMerging #14341 will not alter performanceComparing Summary
Footnotes |
martrapp
left a comment
There was a problem hiding this comment.
Looks very good to me, Chris!
Handmade shadow roots, so that they are declarative for everybody else!
Tried hard to suggest any improvements, but can't. Perfect.
Complete with tests, and comments, and ... and wait ... CHANGESET?
|
I agree this requires no docs change, but it would be nice if people who where looking for DSD support would know that the wait is over ;-) |
Well spotted! Added one.
That’s what the changeset is for 😃 |
Changes
<ClientRouter>#14340<ClientRouter>usesDOMParserto parse the HTML fetched by the router, but this does not support attaching declarative Shadow DOM (<template>elements using theshadowrootmodeattribute) the same way as browsers do when pages load normally.document.parseHTMLUnsafe(), but that would be more disruptive to our code (especially as it’s not widely supported yet so would need a polyfill), so instead I left theDOMParseruntouched and manually upgrade any templates in theswapBodyElement()function.Testing
New E2E test in the view transition fixture.
c1317b0which adds only the new test: ❌ test run2d49c8c, which adds logic to attach shadow roots during transitions: ✅ test runDocs
N/A — bug fix.