The Firefox implementation of chromestatus requires an update, which has 
already shipped in Firefox 114.

在2025年8月11日星期一 UTC+8 17:02:53<[email protected]> 写道:

> Hi,
>
> The CL has been merged and this feature is now available behind the 
> *CSSLangExtendedRanges* runtime flag.
>
> Best,
> Felipe
>
> On Monday, 7 July 2025 at 14:06:41 UTC+9 [email protected] wrote:
>
>> Hi,
>>
>> After coordinating with my colleague Roger Zanoni, I will continue the 
>> development and shipping of this feature.
>>
>> In the previous discussion, two years ago, one of the concerns was that 
>> the lack of sufficient WPT tests.
>>
>> Fortunately, at the moment there are 25 WPT tests for the :lang selector 
>> level 4:
>>
>>
>> https://github.com/web-platform-tests/wpt/tree/master/css/selectors/selectors-4
>>
>> All 25 of these tests pass in Firefox, while 3 of them fail in Safari:
>>
>> https://wpt.fyi/results/css/selectors/selectors-4
>>
>> The implementation is being developed in this CL:
>>
>> https://chromium-review.googlesource.com/c/chromium/src/+/6677873
>>
>> I have assigned myself to the tracking bug at:
>>
>> https://issues.chromium.org/issues/40811938
>>
>> Kind regards,
>> Felipe
>>
>> On Tuesday, 11 April 2023 at 12:09:00 UTC+9 [email protected] 
>> wrote:
>>
>>> On 4/8/23 05:15, Jonathan Kew wrote: 
>>> > Looking at the webkit tests, I"m concerned that some of them may 
>>> conflict with 
>>> > the spec (as I understand it), and this presumably reflects an issue 
>>> with 
>>> > webkit's implementation. 
>>> > [...] 
>>> > and BCP47 specifically mentions that 
>>> > 
>>> >> the language tags described in this document are sequences of 
>>> characters from 
>>> > the US-ASCII [ISO646 <
>>> https://www.rfc-editor.org/rfc/rfc5646#ref-ISO646>] 
>>> > repertoire 
>>> > 
>>> > From this, I would conclude that a string containing non-ASCII 
>>> characters 
>>> > cannot be a "language tag" per BCP47 at all, and therefore cannot 
>>> possibly match. 
>>>
>>> I'm not sure that behavior's wrong, so much as undefined then? 
>>>
>>> I'm OK with either treating non-ASCII tags as not matching, or passing 
>>> them 
>>> through; but that's probably something to discuss in a CSSWG issue with 
>>> i18nWG 
>>> input. 
>>>
>>> ~fantasai 
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a9a82f55-5bc0-46d0-a5ea-b0a7d49f54c3n%40chromium.org.

Reply via email to