This repository has been archived by the owner on Sep 14, 2021. It is now read-only.
Auto style scoping and class scoping #25
Merged
Conversation
This file contains 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
First pass at scope removal.
Conflicts: shadycss.min.js shadycss.min.js.map
…ected connected state at processing time. Add comments and slight factoring.
… an element is actually in a shadowRoot when processing attachment.
This was referenced Nov 9, 2016
Merged
dfreedm
approved these changes
Nov 9, 2016
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Helps address #3 by implementing a MutationObserver to scope dynamic dom changes based on elements being added/removed from the document.
An api is also provided (
setElementClass(element, classString)) that can be used to implement dynamic scoping forclass/className. This will be used by ShadyDOM to transparently scope elements based on changes toclass.