- From: Greg Whitworth via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Feb 2021 03:14:42 +0000
- To: public-css-archive@w3.org
@emilio as noted in the meeting you wanted to work on this and I don't want to be a blocker here in any way. Given that I expect the indicator pseudo with base styles to be a required resolution to standardize these pseudo elements in a meaningful way (eg: the necessary restrictions) I recommend we land on a clear solution there. Relevant issues: - [Base Styles]()https://github.com/w3c/csswg-drafts/issues/5998 - [Indicator Pseudo](https://github.com/w3c/csswg-drafts/issues/5914) - [Indicator Explainer](https://github.com/salesforce/standards-explainers/blob/master/indicator-psuedo/explainer.md) So here's the steps we need to take to finalize this: 1. Standardize a base style switch of some form (see above issue) 2. Define range anatomy in full (even though we know the above 3 are covered via the 3 listed) 3. Define the default styles for the full anatomy This does a few things, this fills the gap I requested earlier regarding the limitations as once we have a base set of styles there actually aren't any limitations to the author outside of fully replacing the content with complex HTML but that can come later. @emilio can you please review the base style issue above - give your feedback and then we can move on to step 2? Let me know if you have any questions. -- GitHub Notification of comment by gregwhitworth Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4410#issuecomment-783022435 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 February 2021 03:14:44 UTC