Skip to content
This repository has been archived by the owner on May 17, 2024. It is now read-only.

Find a better methodology for CSS so we stop having problems with scoping #326

Closed
marinaaisa opened this issue Nov 25, 2019 · 3 comments
Closed
Assignees

Comments

@marinaaisa
Copy link
Contributor

No description provided.

@y4izus
Copy link
Contributor

y4izus commented Nov 26, 2019

Could you specify more about this issue? I've already fixed one problem about the scoping and I wanted to know if it's the same. I found that the scope in some component wasn't working because of the compilation of the selectors from something like .a to something like .a[data-v-f3f3eg9]. If we want to have styles for selectors that are child of .a we should use a deep selector. See this explanation.

For more information:

@marinaaisa
Copy link
Contributor Author

Hey @y4izus, since @delapuente explained you about what I'm doing, I will guess that your question is already answered. Anyways, for anyone who wants to understand what this issue is about:
I'm searching for CSS methodologies/architectures to:

  • Solve component encapsulation problem
  • Minimize CSS size on production to improve our web performance
  • Solve naming problem
  • Only use variables based on a design system

@delapuente
Copy link
Contributor

We solved the problem of scoping in #343, closing this in favour of testing new methodologies in #327

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants