Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Styles position and specificity #16

Open
bleuebuzz opened this issue Sep 16, 2014 · 0 comments
Open

Styles position and specificity #16

bleuebuzz opened this issue Sep 16, 2014 · 0 comments

Comments

@bleuebuzz
Copy link

I think there is two problemes with one file components' styles:

  1. styles are added after exisiting ones in the head. I think styles should be placed on top of the head. They'll acte more as "default styles" for component.
  2. attribute selectors don't replace selectors but are added to them causing more specificity.

The second point could be more tricky to solve as you can't simply replace all selectors by a corresponding attribute selector (contextual selectors for eg). Here two ideas (failing solution):

  • Maybe a solution could be to only replace class selectors (and adding rvcuid to those).
  • Maybe allowing to manually specify temporary rvcuid which will be replaced in both element and selectors with a "strongest" one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant