-
Notifications
You must be signed in to change notification settings - Fork 8
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
Issue with our guidance of use of custom properties #8
Comments
Thank you Daniel for raising this. FWIW, I see this as an issue with custom properties, not an issue with the guidance. The guidance is very sound and correct, we just need to make sure the platform can support it. |
Ok thanks for the clarification Lea – I mostly wanted to create an issue so we could have an anchor to discuss at the future TAG meting call. Do you think we should make a note in the document to reflect the issue? |
This issue is also relevant: WICG/webcomponents#856
Yes. |
Now that I'm here, I'm wondering if we could pick this up in a breakout soon, or the F2F? I want to make sure this guidance can be followed by authors, otherwise we are setting them up for failure. |
https://www.w3.org/2001/tag/doc/webcomponents-design-guidelines/ "Don’t use custom attributes for styling, like bgcolor. Instead use Custom Properties or CSS Shadow Parts." |
Note that container queries allow for style queries too, so this guidance may be possible to follow in the near future (or at least more feasible for more cases). |
From https://twitter.com/LeaVerou/status/1316353717688557571 from @LeaVerou:
The text was updated successfully, but these errors were encountered: