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

CSS spelling and grammar features #470

Open
delan opened this issue Jan 6, 2021 · 4 comments
Open

CSS spelling and grammar features #470

delan opened this issue Jan 6, 2021 · 4 comments
Labels
w3c Specifications in W3C Working Groups.

Comments

@delan
Copy link

delan commented Jan 6, 2021

Request for Mozilla Position on an Emerging Web Specification

Other information

While these features span two specs, they might be worth considering together, because the new pseudo-elements depend on the new text-decoration-line values for UA stylesheet support (and to be most useful to authors).

@emilio
Copy link
Collaborator

emilio commented Jan 12, 2021

cc @jfkthame

@emilio
Copy link
Collaborator

emilio commented Jan 12, 2021

One question, is the intention for the matching / inheritance behavior to match ::selection? And if so, the current browser behavior or the behavior that is in the spec, which is significantly different?

@delan
Copy link
Author

delan commented Jan 14, 2021

One question, is the intention for the matching / inheritance behavior to match ::selection? And if so, the current browser behavior or the behavior that is in the spec, which is significantly different?

Yes, the processing model would be the same as ::selection. I didn’t realise at the time that the current spec behaviour wasn’t implemented by anyone yet^. I think it would be ok to start prototyping under the current impl behaviour (because they would still be usable enough to play around with), but reconcile the gap (changing either spec or impl) before we ship. That might mean gating the pseudos behind a flag, to avoid adding to the backwards-compatibility risk we already have with ::selection.

^ I would really appreciate some of your time to ask you about that actually. I spent a few days reading how the behaviour evolved, but a lot of the terminology was new to me, so I’m still not sure I’ve understood the nuances correctly. If you’re interested, let me know what medium works best for you. Thanks!

@annevk annevk added the w3c Specifications in W3C Working Groups. label Mar 12, 2021
@delan
Copy link
Author

delan commented Jul 1, 2021

I’ve created a separate issue (#548) about the highlight processing model.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
w3c Specifications in W3C Working Groups.
Projects
None yet
Development

No branches or pull requests

3 participants