fix(framework): Do not create IE styles with disabled #2284
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
ilhan007
approved these changes
Oct 1, 2020
fifoosid
approved these changes
Oct 1, 2020
vladitasev
added a commit
that referenced
this pull request
Oct 2, 2020
ilhan007
pushed a commit
that referenced
this pull request
Oct 17, 2020
ilhan007
pushed a commit
that referenced
this pull request
Nov 11, 2020
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.
Do not create component styles for IE11 with
disabled, because if they don't contain at least one CSS Variable, they will not be processed by the CSS Vars ponyfill. It will skip them, and not create new styles with the compiled static CSS. Thus they will remaindisabledand not have any effect on the page.The bug can only be seen with components that don't have at least one CSS Var in their styles.
closes: #2283