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?`.

<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<br>
&lt;dael> Rossen_: fantasai or AmeliaBR can you summarize?<br>
&lt;dael> fantasai: Let's see where we're at<br>
&lt;dael> florian: I thought semi reviewed and waiting for additional feedback<br>
&lt;dael> fantasai: Yeah<br>
&lt;AmeliaBR> I'm not sure there's much more to discuss. Needs proposed text.<br>
&lt;dael> florian: I think agenda+ was left on rather then added<br>
&lt;dael> Rossen_: Bot didn't resolve?<br>
&lt;dbaron> the bot only removes agenda+ when there's a resolution, btw<br>
&lt;dael> Daniel: I had a chance to digest this. We described in terms of currentColor<br>
&lt;dael> Daniel: I wrote a comment, so to restate. currentColor would solve this and for all color properties, but not for caret and text shadow<br>
&lt;dael> Daniel: In 2.2 of the same spec we solved this for the first letter<br>
&lt;dael> fantasai: first letter is different kind of psuedo element. It inherits fundimentally through the tree. What we're doing for selection, a selection for a span inherits from the p, not the span. That has to happen for all the different properties that inherit<br>
&lt;dael> Daniel: I read 2.2 and how it's impl in webkit<br>
&lt;dael> fantasai: Webkit impl isn't like any other browser<br>
&lt;dael> Daniel: I like webkit where you cascade and then inherit<br>
&lt;dael> fantasai: The thing currently impl, if you have selections like &lt;p>::selection and inside the p you have a span, you lose the selection over the span<br>
&lt;dael> Daniel:Currently in webkit?<br>
&lt;dael> fantasai: That's in every other browser<br>
&lt;dael> Daniel: That doesn't happen. I could be wrong, but in my memory of code that's not what happens. For the span...we do the cascade, find the parent with the section...right now we do the cascade<br>
&lt;fantasai> testcase his is some emphasized tex<br>
&lt;fantasai> http://software.hixie.ch/utilities/js/live-dom-viewer/?&lt;!DOCTYPE%20html>%0A&lt;style>%0Ap%3A%3Aselection%20%7B%20background%3A%20green%3B%20%7D%0A&lt;%2Fstyle>%0A&lt;p>this%20is%20some%20&lt;em>emphasized%20text&lt;%2Fem><br>
&lt;dael> Daniel: I would like what webkit does for first letter. It cascades first and then does inheritance against first line.<br>
&lt;dbaron> I don't know what you mean by "does the cascade" -- cascading what together?<br>
&lt;dael> Daniel: If you had some span that has a first letter and it's inside a parent with a first letter inside a parent with a first line, you cascade for first letter and inherit from cascade result of first line. THat's my interpretation of section 2.2<br>
&lt;dael> fantasai: 2.2 jsut changed<br>
&lt;dael> florian: The thing fantasai just pasted run in safari agrees with what fantasai stated about current behavior.<br>
&lt;fantasai> Cascading / inheritance model for ::selection was changed in https://github.com/w3c/csswg-drafts/issues/2474<br>
&lt;dael> florian: In the spec we're trying to get away from yest it's different then current, but current aren't useful. If you're trying to style ::selection applied to particular elements it breaks if they have children. That's why we want different model<br>
&lt;dael> Daniel: One thing; did fantasai post the example? I can explain. That's broken. I have a patch for webkit. WE only do it for first-letter and first-line. I'm saying why can't we make selection have same model as first-line<br>
&lt;dael> fantasai: That's a different issue, that's about fundimental inheritance and cascade for selection. That still is a thing that needs to be defined<br>
&lt;dael> Daniel: I filed this issue because I wanted to solve<br>
&lt;dael> fantasai: There is an issue where we're discussing in general. You can compare the model. One is cascade one is inheritance. Both are discussed and you can see both in spec. Cascade is in the TR and inheritance is in the ED<br>
&lt;dael> Daniel: I'll read it and comment on it<br>
&lt;dael> florian: To add one thing, the one on TR is what was previous and the new on is in the ED because we objected to doing it the cascade way<br>
&lt;dael> Daniel: Let me read through both and I'll discuss in github<br>
&lt;dael> Rossen_: Excellent. Thank you for chiming in.<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-454868060 using your GitHub account

Received on Wednesday, 16 January 2019 17:31:37 UTC