Re: [csswg-drafts] [selectors] `:lang` for documents without content language and for elements of unknown language; consider `:lang("")` over `:not(:lang("*"))` (#6915)

The CSS Working Group just discussed `:lang() without document language`.

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> Topic: :lang() without document language<br>
&lt;TabAtkins> fantasai: When a lang is unknown, there's two ways ot make it unknown<br>
&lt;TabAtkins> fantasai: first is blank `lang` value<br>
&lt;TabAtkins> fantasai: second is `lang=und`<br>
&lt;TabAtkins> fantasai: So how do you match these elements?<br>
&lt;TabAtkins> fantasai: Proposal is `:lang("")` matches untagged (blank tag), and add a note that `"und"` and `""` are matched differently despite similar semantics<br>
&lt;TabAtkins> fantasai: And then `:lang("*")` will match any tagged element, including `lang=und` (but won't match untagged/empty string)<br>
&lt;TabAtkins> TabAtkins: Sorry, hadn't read the discussion, but what's the justification for treating empty string differently from und?<br>
&lt;fantasai> Rossen: I'm not sure about treating them differently<br>
&lt;PaulG> which spec does "und" value come from?<br>
&lt;fantasai> Probably BCP47<br>
&lt;TabAtkins> Rossen_: Is it in selectors, or text...?<br>
&lt;TabAtkins> fantasai: und is in the lang tag spec<br>
&lt;TabAtkins> PaulG: rfc 5646 doesn't have it, it's not in the IDN reg<br>
&lt;TabAtkins> Rossen_: Perhaps we should delay a week for florian to be able to weigh in<br>
&lt;dbaron> und looks like it's for undetermined<br>
</details>


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 October 2022 16:16:16 UTC