- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Jul 2020 16:57:31 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-lists-3][css-pseudo-4] Does text-transform inherit to ::marker?`, and agreed to the following:
* `RESOLVED: add ::marker { text-transform: none; } to UA stylesheet, at least for now`
* `RESOLVED: text-transform applies to ::marker`
<details><summary>The full IRC log of that discussion</summary>
<dael> Topic: [css-lists-3][css-pseudo-4] Does text-transform inherit to ::marker?<br>
<dael> github: https://github.com/w3c/csswg-drafts/issues/4206<br>
<dael> fantasai: One browser blocks inheritance of list marker<br>
<dael> fantasai: Blocking text-tranform makes sense. ::marker means UA should set text-transform:none and author can set to inherit. But default it should not inherit.<br>
<florian> +1<br>
<dael> fantasai: I want to go through text-transform before other properties<br>
<TabAtkins> +1 to text-transform<br>
<dael> oriol: Not sure I agree. test-transform applies to text like color. If you set color it's inherit, why should text-transform be different? For ::before and ::after it inherits. If you set something case sensitive you would close it. Why should marker be different<br>
<Rossen_> q?<br>
<dael> florian: In general we don't know if text is case sensitive but we do know markers are<br>
<dael> TabAtkins: Agree with fantasai and florian where we have 2 pairs of markers that are explicitly case sensitive. Having text-transform for in is likely unitnentional. Having it automatically it may make it confusing to read. Should be allowed to set<br>
<dauwhe> q+<br>
<dael> fantasai: Can also be semantic where nested lists have some upper and some lower and then they're referenced in other parts of text. If you transform the case it breaks the link. THe default would be safer if we don't have this inherit by default<br>
<dael> dbaron: I think some question if the thing is markers or counter references<br>
<dael> dbaron: I think the thing we're talking about is references to counters which are lower-roman, upper-roman. If we were to have a feature for counter references then the thing we want to not be transformed is the counter reference.<br>
<dael> dbaron: If rule in css is the counter references are not text transformed there's no way for author to say they really do want.<br>
<dael> fantasai: INteresting point. Advocate a separate issue for that. In meantime set text-transform to none so we get markers as defined today<br>
<florian> +1<br>
<dauwhe> q-<br>
<dael> dauwhe: Author PoV I found it surprising that i do something to list item and changes list numbering<br>
<dael> oriol: Should we allow it to list of properties allowed in markers so authors can set to inherit?<br>
<dael> fantasai: Yes, that's part of proposal<br>
<dael> Rossen_: Nearing a resolution. Other questions or PoV?<br>
<dael> Rossen_: If not I'll ask if there are objections.<br>
<dael> oriol: Should we discuss other properties in issue? Text-indent seems more obvious<br>
<dael> fantasai: Let's not all properties together. Let's do one and move to next<br>
<dael> TabAtkins: Unless you think they're linked.<br>
<dael> Rossen_: Do you believe they should be linked?<br>
<dael> oriol: Independent<br>
<dael> Rossen_: Objections?<br>
<dael> fantasai: text-transform is #4558<br>
<dael> florian: You mean text-indent?<br>
<dael> Rossen_: Where should the resolution go?<br>
<dael> fantasai: Here.<br>
<fantasai> s/text-transform/text-indent/<br>
<dael> text-indent is separate<br>
<fantasai> https://github.com/w3c/csswg-drafts/issues/4206<br>
<dael> dbaron: I think at some poitn there was sumamry of existing impl<br>
<dael> dbaron: Trying to understand that state<br>
<dael> fantasai: Top of issue<br>
<dael> dbaron: Claim Gecko blocks inheritence of text-transform. Do we support text-transform:inherit?<br>
<dael> oriol: In chromium markers if you use content:normal it uses ns bullet which doesn't support text-transform. Content to something different than normal it's a different box and it inherits like Chromium. If you set it to something else it will also do that<br>
<dael> dbaron: I think implication is trying to resolve on something done by some impl. I don't think that's the case<br>
<oriol> s/In chromium/In Gecko<br>
<dael> fantasai: I think there's some spec in what's impl. Effect on existing pages...features where we don't have the behavior are new and not much used. Discussion in the issue but I concluded we shoudl block text-transform on markers<br>
<dael> dbaron: Rather than say it doesn't apply to counter references<br>
<oriol> s/ns bullet/nsBulletFrame<br>
<dael> fantasai: Until that's defined I think it's important to not establish a precedence in the majority of cases with markers<br>
<dael> dbaron: Okay<br>
<dbaron> (I think I probably prefer tying this to counters than to markers, but I don't object.)<br>
<dael> Rossen_: Going back, any new objections from this conversation?<br>
<TabAtkins> I could see a list style that's like "First: ", "Second: ", etc., which is fine to text-transform and probably *expected* to respond to that. Maybe this does need to go into the @counter-style definition, like dbaron's earlier comments suggested...<br>
<fantasai> RESOLVED: add ::marker { text-transform: none; } to UA stylesheet, at least for now<br>
<fantasai> TabAtkins, dbaron: yeah, I could live with that... but I'm not sure how we're going to make that work yet, and until we do I think this is a good move<br>
<dael> Rossen_: Next set of properties in the issue?<br>
<fantasai> https://github.com/w3c/csswg-drafts/issues/4568<br>
<dael> fantasai: Separate issue open which is #4568 which discusses all properties<br>
<fantasai> https://github.com/w3c/csswg-drafts/issues/4568#issuecomment-562734422<br>
<dael> fantasai: I suggest we continue there.<br>
<dael> fantasai: My take is we need to define what is inherited through ::marker vs properties that are for paragraph or line box. Properties for block containers shouldn't be for ::marker. Once we define the interesting question is if word-spacing or letter-spacing is also reset.<br>
<dael> fantasai: Not sure we should take it now.<br>
<dael> florian: Given resolution we took I think we need to say text-transform applies to ::marker<br>
<dael> fantasai: Sure<br>
<dael> florian: We said we'd put the property in the UA stylesheet without saying to property applies<br>
<dael> fantasai: Does it apply to marker or text. Need clarity<br>
<dael> florian: That is applies somehow needs to be resolved<br>
<dael> fantasai: Sure<br>
<dael> Rossen_: What's the proposa?<br>
<dael> florian: text-transform applies to ::marker<br>
<dael> Rossen_: Thoughts or objections?<br>
<dael> RESOLVED: text-transform applies to ::marker<br>
<dael> Rossen_: fantasai you asked if we should open #4568 about which properties reset?<br>
<dael> fantasai: I think today we should move on<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4206#issuecomment-658881841 using your GitHub account
Received on Wednesday, 15 July 2020 16:57:33 UTC