- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Sep 2020 16:39:22 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-content] Quote character choice must depend on surrounding language, not language of the quotation`, and agreed to the following:
* `RESOLVED: auto value of quote to be based on parent language`
* `RESOLVED: Add match-parent keyword`
<details><summary>The full IRC log of that discussion</summary>
<dael> Topic: [css-content] Quote character choice must depend on surrounding language, not language of the quotation<br>
<dael> github: https://github.com/w3c/csswg-drafts/issues/5478<br>
<dael> fantasai: The question raised is we have an atuo keyword for quotes property. Richard points out set you want to use is the set of the parent, not the element's language<br>
<tantek> wow I thought we solved that with the Q element back in the day<br>
<dael> fantasai: Do we want to resolve to define auto value of quote to choose based on parent's content language rather then element's content language?<br>
<dael> Rossen_: Comments?<br>
<fantasai> tantek, this is how the Q element is implemented<br>
<fremy> this seems to make sense<br>
<dael> ??: Works for me and I see Richard's point. Good issue.<br>
<faceless2> s/??/faceless2<br>
<dael> tantek: Agree as well. I thought we did that in E5 Mac for Q element. We should look at Q element<br>
<dael> fantasai: Q element is defined in CSS terms. So we need to fix our spec.<br>
<tantek> s/E5/IE5<br>
<dael> Rossen_: Objections to resolve auto value of quote to be based on parent language<br>
<dael> RESOLVED: auto value of quote to be based on parent language<br>
<dael> fantasai: Second part of issue<br>
<fantasai> https://github.com/whatwg/html/issues/3636#issue-316269336<br>
<fantasai> But Lucy replied: “Embrassez George de ma part et dites-lui, ‘Embrouille’”<br>
<dael> fantasai: If you have quote within a quote you will typically use quotation style of contextual language not immediate parent.<br>
<dael> fantasai: Previously when didn't have auto some discussion on how to do that with selectors and ^ have examples<br>
<dael> fantasai: auto inherits as itself. No way to get that behavior of I am using the quotation marks of my context.<br>
<dael> fantasai: Can get the behavior but need keyword like match-parent. Aline has that to use same resolved alignment as parennt<br>
<florian> s/Aline/align/<br>
<dael> fantasai: We added match-parent which says look at my parent value and if it's phsyical inherit. Logical resolve and inherit<br>
<florian> s/Aline/text-align/<br>
<dael> fantasai: Can do similar here where if my parent value is similar to quote inherit. If it's auto, resolve that to a string and set my computed value to that string and it inherits through.<br>
<Rossen_> q<br>
<dael> florian: Would that be what match-parent does? I think you want to match style but not string.<br>
<AmeliaBR> Quotes already need to keep track of nesting, so can't auto have a behavior that if this is a nested quote, use the same language quotes as the outer level?<br>
<dael> fantasai: Nesting if from open/close quote<br>
<dael> florian: Yes, yes.<br>
<dael> fantasai: Keeping track of nesting we don't have to worry about here. Nesting levels is defined and UA is responcible to choose correct.<br>
<dael> fantasai: Do we want to add a match-parent keyword?<br>
<florian> I think we do<br>
<fantasai> s/define/handled by counters built into the content property/<br>
<dael> Rossen_: I see one support on IRC<br>
<dael> Rossen_: Other thoughts or reasons why we shouldn't?<br>
<dael> jfkthame: Unclear. Is match-parent inUA stylesheet or authors expected to do?<br>
<dael> fantasai: I don't know the answer. If want behavior where using quotation lang of context it's easy in UA stylesheet. That should get correct behavior. If we want that in UA stylesheet I'm less sure but I leave that to i18n and WhatWG. This makes it possible to do<br>
<fantasai> s/that should/q q { quotes: match-parent; } should<br>
<dael> florian: Seems that if we want q element to be able to have the range of behaviors needed to use it properly we should do this. If we believe people don't use q element maybe we can skip, but if we want it to be useful we should do this.<br>
<dael> jfkthame: Then we should do it. I think it's a useful property<br>
<fantasai> s/jfkthame/faceless2/<br>
<dael> Rossen_: hearing people leaning toward the optional keyword match-parent.<br>
<dael> Rossen_: Thoughts of objections to adding match-parent keyword?<br>
<dael> RESOLVED: Add match-parent keyword<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5478#issuecomment-701507076 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 September 2020 16:39:25 UTC