Open
Conversation
added 3 commits
July 12, 2018 21:10
…n with other style computing / remove as much mixin as possible + dead code
…animation with other style computing / remove as much mixin as possible + dead code" This reverts commit f6ee91d.
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
1 participant
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.
The main reason I would like to remove this custom-styles tag is for performance, it is using polyfills and it is a heavy one to compute.
https://www.polymer-project.org/2.0/docs/devguide/style-shadow-dom
You should only use custom-style to define styles for the main document. To define styles for an element's local DOM, just use a <style> block.