On 10/16/26 2:22 p.m., Daniel Vogelheim wrote:
On Thu, Oct 15, 2026 at 6:55 PM Mike Taylor <[email protected]>
wrote:
On 10/14/26 12:11 p.m., Chromestatus wrote:
*Interoperability and Compatibility*
/No information provided/
/Gecko/: No signal
I see this shipped in Firefox:
https://bugzilla.mozilla.org/show_bug.cgi?id=2068934#c9 - can you
update the chromestatus entry?
Done.
/WebKit/: No signal
Can we request a signal please?
Are you sure? WebKit has not implemented the underlying feature
(Sanitizer API, position here
<https://github.com/WebKit/standards-positions/issues/86>), so they're
unlikely to have strong opinions about this particular sub-feature.
The spec change has landed in HTML, which I take it means some amount
support from all standardizers.
This is more helpful context for reviewers than just "no signal". :)
That said, "they don't ship this" isn't a super strong reason to not
file a request (it may be useful for them to know that we are shipping
this change), but you could also leave a comment on the existing signal
if you prefer.
*Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?*
No
Why not?
Tests are here:
https://wpt.fyi/results/sanitizer-api/sanitizer-javascript-url.html
*Finch feature name*
/No information provided/
Is this just omitted?
SanitizerJavascriptURLs
All items are also updated directly in Chromestatus.
--
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/88a23bd3-1535-4c61-a236-464be90163ff%40chromium.org.
