W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2020

Re: [csswg-drafts] [css-text-3][css-fonts-3][css-text-decor-3] Distinguish applying to text vs applying to boxes (#5303)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 22 Oct 2020 16:00:16 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-714593347-1603382412-sysbot+gh@w3.org>
The CSS Working Group just discussed `Distinguish applying to text vs applying to boxes`, and agreed to the following:

* `RESOLVED: inheritable properties that apply to inlines also apply to text`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen_> Topic: Distinguish applying to text vs applying to boxes<br>
&lt;Rossen_> github: istinguish applying to text vs applying to boxes<br>
&lt;Rossen_> github: https://github.com/w3c/csswg-drafts/issues/5303<br>
&lt;fremy> fantasai: it's not super clear which property apply to text, and which apply to inline boxes<br>
&lt;fremy> fantasai: the specs sometimes says one when they mean the other<br>
&lt;TabAtkins> testcase from oriol showing off the distinction:<br>
&lt;TabAtkins> https://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Asection%20%7B%20border%3A%201px%20solid%20%7D%0Adiv%20%7B%20line-height%3A%204%3B%20display%3A%20contents%20%7D%0A%3C%2Fstyle%3E%0A%3Csection%3E%3Cdiv%3Eline-height%20inherited%20by%20text%3C%2Fdiv%3E%3C%2Fsection%3E%0A%3Csection%3E%3Cdiv%3E%3Cspan%3Eline-height%20inherited%20by%20inline%20box%3C%2Fspan%3E%3C%2Fdiv%3E%3C%2Fsection%3E<br>
&lt;fremy> fantasai: but for some properties we need a distinction<br>
&lt;TabAtkins> chrome renders the two boxes the same, firefox doesn't apply line-height to the first (where there is no box to apply to, only text)<br>
&lt;fremy> fantasai: I propose to make a mass update to say "text" vs "inline boxes" vs "inline boxes and text"<br>
&lt;fremy> fantasai: text decoration, color, etc...<br>
&lt;fremy> fantasai: this will require some auditing of the existing propdef tables<br>
&lt;fremy> florian: I initially agreed<br>
&lt;chris> seems good to me, I think it is clearer<br>
&lt;fremy> florian: but oriol made a test case and it confused me<br>
&lt;fremy> florian: because content makes an anonymous inline<br>
&lt;fremy> florian: so what's the difference between the two concepts, I am not sure<br>
&lt;fremy> fantasai: is there an anonymous inline? really?<br>
&lt;fremy> TabAtkins: as far as I know, there is not<br>
&lt;fremy> florian: ah ok, then we need to specify<br>
&lt;fremy> emilio: webkit allows display:contents on text, but we don't in gecko<br>
&lt;fremy> TabAtkins: do you think this makes a different except line-height?<br>
&lt;fremy> emilio: no, apart from that, I don't think there is a difference<br>
&lt;fremy> florian: and the whitespace property?<br>
&lt;fremy> florian: if there is no inline box? how would that work?<br>
&lt;fremy> emilio: I would have to test<br>
&lt;fremy> emilio: I remember we used to apply only the closest inline container<br>
&lt;fremy> emilio: and we changed this, but I don't recall the specifics<br>
&lt;Rossen_> q<br>
&lt;fremy> oriol: one of the principles we should try to follow is to use inheritance as a rule<br>
&lt;fremy> oriol: otherwise there could be differences if you have or not the inline<br>
&lt;fremy> TabAtkins: that sounds like a reasonable rule to me<br>
&lt;fremy> TabAtkins: and whitespace works in firefox<br>
&lt;fremy> Rossen_: so could line-height be a bug in gecko?<br>
&lt;fremy> florian: did the list you made match oriol rule?<br>
&lt;fremy> fantasai: I think so, but the list was very rough I didn't take a full look<br>
&lt;fremy> fantasai: there might be issues with alignment<br>
&lt;fremy> fantasai: but we can take a look later<br>
&lt;fremy> florian: I support resolving oriol rule then<br>
&lt;fremy> florian: and we can revisit if needed later<br>
&lt;fremy> Rossen_: and we need to add this rule?<br>
&lt;fremy> florian: yes, we should indeed do that, there is no text now<br>
&lt;fremy> Rossen_: ok, sounds go<br>
&lt;fremy> Rossen_: who will do that?<br>
&lt;fremy> florian: it could be me, but I am not sure when<br>
&lt;fremy> fantasai: ok I will take this<br>
&lt;fremy> Rossen_: ok, thanks<br>
&lt;fremy> Rossen_: do we need a resolution for oriol's rule?<br>
&lt;fremy> fantasai: yes, if we need exceptions we will revisit?<br>
&lt;fremy> Rossen_: ok, any objections to add this rule?<br>
&lt;fremy> fantasai: and update the propdef tables<br>
&lt;fremy> RESOLVED: inheritable properties that apply to inlines also apply to text<br>
&lt;florian> s/ but I am not sure when/ but it doesn't have to/<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 22 October 2020 16:00:19 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:20 UTC