Re: [csswg-drafts] [css-pseudo-4]: How should a selected spelling error be painted? (#2850)

The CSS Working Group just discussed `How should a selected spelling error be painted?`, and agreed to the following:

* `RESOLVED: specify the current behavior and use the currentColor name`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: How should a selected spelling error be painted?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2850#issuecomment-454870849<br>
&lt;dael> Rossen_: It's a level 4 quesiton<br>
&lt;dael> fantasai: I think this was about defining currentColor to represent color of the previous layer. You have the document which has colors for text and then spelling error and the selection layered on top. Proposal was use currentColor keyword to use the color. This seemed a neat way to represent that concept<br>
&lt;dael> fantasai: Given the way inheritance is working in the ::selection tree<br>
&lt;dael> florian[m]: Model makes sense to me. COncept of layers is that abstract way to desc or do impl work like that?<br>
&lt;dael> fantasai: Impl I do't know how they work, selection is only thing impl. Selection is painted over rest of doc. Text that spec how thigns is painted say it's painted over, but it's really in replacement of original text. If each pseudo element spec a color, only last will paint the text<br>
&lt;dael> fantasai: That's a sep question on how things are painted. THis is can we use currentColor to be the color I would otherwise be or do I need a new keyword?<br>
&lt;Rossen_> https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/master/highlight/explainer.md<br>
&lt;dael> Rossen_: There was an explainer that I was told would be proposed and discussed soon ^<br>
&lt;dbaron> I'm a little worried this might be too clever...<br>
&lt;dael> Rossen_: You may or may not have gone through it. I'm raising awareness of something discussed in context of editing<br>
&lt;dael> Rossen_: This is being worked on more actively and there is some interaction with CSS for styling and handling of overlays and colors.<br>
&lt;dael> Rossen_: I was a little involved in the beginning so this proposal is at least in a sane state it's in currently. If fantasai you were looking for new words this could be a good primer to see if we can extract something<br>
&lt;dael> fantasai: This is about defining new layers. In the section linked from the explainer it's future custom pseudos. This isn't new layers of highlights. This is how to a rep in the CSS properties model the color for a highlight that's 'don't give me a color'. I think most striaghtforward is currentColor keyword.<br>
&lt;dael> fantasai: On color it says inherit from whatever I inherit from. That would be the ::selection's parent. We need to a way to say ::Selection doesn't have a color. WE can do magic and say you can't spec that, or we use this, or I invent a new word<br>
&lt;dael> florian[m]: Using currentColor makes sense. The thing from Rossen_ doesn't change that<br>
&lt;dael> dbaron: This is only doing something special for currentColo on the color property, not any other uses?<br>
&lt;dael> fantasai: Yeah b/c rest will refer to color property<br>
&lt;dael> dbaron: That makes it seem a little less scary<br>
&lt;dbaron> s/currentColo/currentColor/<br>
&lt;dael> Rossen_: Some support for currentColor<br>
&lt;dael> Rossen_: Objections to specify the current behavior and use the currentColor name?<br>
&lt;fantasai> Note to self: clarify dbaron's point<br>
&lt;dael> RESOLVED: specify the current behavior and use the currentColor name<br>
&lt;dael> florian[m]: I'm very interested in that explainer and I'll look into this. It's great that you're doing it it was on my to do list<br>
&lt;dael> Rossen_: Please do, this is getting traction.<br>
&lt;dael> Rossen_: Discussion is on WCG or Editing TF<br>
&lt;fantasai> This is why we have templates that define where the discussion happens<br>
&lt;dael> gregwhitworth: I think it's Editing TF<br>
&lt;dael> florian[m]: I'll look there<br>
&lt;dael> Rossen_: If you're really interested I can connect you with folks on our end. Shoot me an email<br>
</details>


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

Received on Wednesday, 30 January 2019 17:25:32 UTC