Re: [csswg-drafts] [css-pseudo] highlight pseudos and emphasis/underline properties (#7101)

The CSS Working Group just discussed `[css-pseudo] highlight pseudos and emphasis/underline properties`, and agreed to the following:

* `RESOLVED: Accept the proposed PR`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> Topic: [css-pseudo] highlight pseudos and emphasis/underline properties<br>
&lt;emeyer> Github: https://github.com/w3c/csswg-drafts/issues/7101<br>
&lt;emeyer> delan: Highlight pseudos have a restricted subset of applicable properties. Not all properties in the text-decoration spec start with text-decoration-*.  Question originally was, can we add those and make them applicable.  I initially thought we should.  fantasai and rego have mentioned most of the text-emphasis-* properties shouldn’t be applicable.<br>
&lt;emeyer> …Maybe only text-emphasis-color should be applied.  That’s where we are now.<br>
&lt;emeyer> astearns: I’m a little worried that the proposed patch is still a little vague.  Should we be very specific about what can be applied?<br>
&lt;emeyer> fantasai: I don’t think we should be very specific, because as more things are added elsewhere, user agents should be free to add them here.  I think the proposed wording is good enough for now.<br>
&lt;tantek> +1 fantasai<br>
&lt;smfr> q+<br>
&lt;emeyer> delan: In general, we’re happy with all the properties related to line decorations being applicable?<br>
&lt;emeyer> fantasai: Right.<br>
&lt;emeyer> delan: So it’s the emphasis marks that are contentious.<br>
&lt;astearns> ack smfr<br>
&lt;emeyer> smfr: Are we avoiding properties that can cause ink or layout overflow?<br>
&lt;emeyer> delan: Ink overflow yes, layout overflow no.<br>
&lt;emeyer> fantasai: Ink overflow doesn’t trigger scrollbars.  We want to avoid anything that could cause scrollbars.<br>
&lt;emeyer> delan: So actually ink overflow no, layout overflow yes.  Sorry, got those backwards.<br>
&lt;emeyer> astearns: Ink overflow is okay, layout overflow is not okay.  We could have a note in the specification saying that’s how we determine the list of properties.<br>
&lt;emeyer> delan: We sort of do say that about the layout, but we could be more explicit about ink overflow.<br>
&lt;iank_> changes in layout overflow implicitly effects layout.<br>
&lt;emeyer> astearns: The bit we have about not affecting overflow layout is sufficient, I think.<br>
&lt;emeyer> RESOLVED: Accept the proposed PR<br>
&lt;fantasai> fwiw   fwiw spec says “The highlight pseudo-elements can only be styled by a limited set of properties that do not affect layout and can be applied performantly in a highly dynamic environment—and additionally (to ensure interoperability) whose rendering within the required area is not dependent on the exact (UA-determined) bounds of the highlight overlay.”<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7101#issuecomment-1124007042 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 11 May 2022 16:47:48 UTC