Thanks all! The WebKit standards position request can be found here,
https://github.com/WebKit/standards-positions/issues/738, and was swiftly
answered
<https://github.com/WebKit/standards-positions/issues/738#issuecomment-6638188575>
.
I've updated Chromestatus accordingly.


On Tue, Oct 27, 2026 at 7:44 PM Alex Russell <[email protected]>
wrote:

> LGTM3 on the same condition.
>
> On Wednesday, October 21, 2026 at 8:20:17 AM UTC-7 Chris Harrelson wrote:
>
>> LGTM2 with the same condition.
>>
>> On Wed, Oct 21, 2026 at 8:15 AM Mike Taylor <[email protected]>
>> wrote:
>>
>>> LGTM1 % getting a WebKit standards position filed.
>>> On 10/21/26 11:14 a.m., Alex Russell wrote:
>>>
>>> Ok, so let's update the bits in the Intent.
>>>
>>> As for Worker parsing, yes, we're all aware. Still needs progress = )
>>>
>>> On Monday, October 19, 2026 at 11:28:39 AM UTC-7 Noam Rosenthal wrote:
>>>
>>> On Mon, Oct 19, 2026 at 7:21 PM Alex Russell <[email protected]>
>>> wrote:
>>> >
>>> > Agree with Mike that we should not extrapolate and should, instead,
>>> file requests to get them on the record. Even strong opposition won't block
>>> us shipping, so there's no risk here of filing
>>>
>>> Mozilla is already shipping this so we can change Gecko chrome status
>>> to "shipping".
>>>
>>> > As for the specific API, it's good to see, but I can't help wonder
>>> when this will be available from Workers. It's the highest priority request
>>> about this API that we hear from teams at MSFT, and lack of this in the
>>> Worker and Service Worker context is a constant bundle bloater.
>>>
>>> Currently workers don't support anything related to the HTML parser.
>>> e.g. It's impossible to create HTML DOM nodes in a worker. e.g.
>>> `DOMParser` is only available in a `Window` context.
>>> This means that the sanitizer is not particularly useful in workers in
>>> isolation.
>>> Either way, this feels a bit orthogonal (though worth exploring).
>>>
>>> --
>>>
>> 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/389577d1-1d59-4754-a657-def07f8bfcc5%40chromium.org
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/389577d1-1d59-4754-a657-def07f8bfcc5%40chromium.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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/CALG6KPNO4znVg0XkFoFnLSqa_szx4irhvHZbCpm7s7UOrjFd4g%40mail.gmail.com.

Reply via email to