Repository navigation
Resolve bounded imported stylesheets natively - #483
Merged
Merged
Conversation
This was referenced Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem and behavior
Imported CSS was ignored by native parsing, linked rules had no owner/source identity, and disconnecting a link could leave its rules in the cascade.
This provider slice resolves leading
@importrules through the existing stylesheet resource policy, preserves nested base URLs and media/layer/supports qualifiers, bounds depth/count/bytes/cycles, retains linked source/address/owner identity, and removes/reconnects owner-bound rules. Private non-enumerable hooks expose the retained source and policy-backed loader to the stacked CSSOM consumer.Stack
CSSImportRule, child sheets, live mutation, and contracts.Validation debt
Per the implementation-throughput directive, build, native/browser/WPT, performance, memory, lifecycle, package, and CI validation were not run. The cumulative stack top carries the regression contracts and all checks remain required before release promotion.
Closes #481