W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [css-inline-3] Improve list of properties applying to initial letters

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Thu, 05 Jul 2018 02:07:10 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-402586492-1530756429-sysbot+gh@w3.org>
The Working Group just discussed `Properties that apply to initial-letter`, and agreed to the following:

* `RESOLVED: approve the edit`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Properties that apply to initial-letter<br>
&lt;fantasai> github: https://github.com/w3c/csswg-drafts/issues/2700<br>
&lt;fantasai> See https://drafts.csswg.org/css-inline-3/#initial-letter-properties<br>
&lt;fantasai> “All properties that apply to an inline box also apply to an initial letter (unless it is an atomic inline, in which case the set of properties that apply to an atomic inline apply) except for vertical-align and its sub-properties, font-size, and line-height. Additionally, all of the sizing properties and box-sizing also apply to initial letters.”<br>
&lt;frremy> fantasai: before was a whitelist, current spec text is more general<br>
&lt;frremy> fantasai: all props except vertical-align, font-size and line-height<br>
&lt;frremy> dbaron: so this includes mpb?<br>
&lt;frremy> fantasai: yes<br>
&lt;frremy> dauwhe: yes<br>
&lt;frremy> florian: so we are just resolving to approve the edit?<br>
&lt;frremy> fantasai: yes<br>
&lt;tantek> is outline in that list<br>
&lt;tantek> ?<br>
&lt;frremy> TabAtkins: our only objection is that this is one more list to maintain<br>
&lt;fantasai> for reference, the old section : https://www.w3.org/TR/2016/WD-css-inline-3-20160524/#initial-letter-properties<br>
&lt;frremy> TabAtkins: and we already keep forgetting to do this for first-letter and first-line<br>
&lt;frremy> TabAtkins: problem happens whether you black list of white list<br>
&lt;frremy> TabAtkins: but the failure mode and the fixed mode of starting from an allow list is better<br>
&lt;frremy> fantasai: we came to the opposite conclusion because most things should apply<br>
&lt;frremy> fantasai: we don't except many new exceptions<br>
&lt;frremy> fantasai: but we expect most things to be useful<br>
&lt;frremy> dauwhe: the blacklist is useful because it is short and enables to grasp the scope of the feature<br>
&lt;frremy> florian: would like a note that explains the principle, so that new properties would be able to be categorized by this rule even if we forget to add them<br>
&lt;frremy> fantasai: but they wouldn't be able to apply because the algorithms don't take them in consideration<br>
&lt;frremy> florian: that was just a proposal, but I'm fine as-is<br>
&lt;frremy> Rossen: so, can we resolve on the blacklist with three properties then?<br>
&lt;frremy> TabAtkins: no objection<br>
&lt;frremy> dbaron: sizing properties apply too?<br>
&lt;frremy> fantasai: this is the next issue<br>
&lt;frremy> dbaron: ok<br>
&lt;frremy> RESOLVED: approve the edit<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2700#issuecomment-402586492 using your GitHub account
Received on Thursday, 5 July 2018 02:07:15 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:53 UTC