To clarify the Chromium timeline, their plan is to turn it off on Stable in 158, which is in November. I assume there are very few sites that have opted in to the origin trial, since it's new and it's still enabled in Stable.
I believe we can't get origin trial participants from them, but we can run a query in httparchive to find such pages (if they're in the dataset). Apart from the origin trial, Chromium has re-enabled <https://chromium-review.googlesource.com/c/chromium/src/+/8224345> XSLT (temporarily) for CAP Alert documents. We could copy this for Nightly if we're worried about annoying Nightly users who view such documents. On Thu, Aug 27, 2026 at 1:23 PM 'Emma Zühlcke' via [email protected] <[email protected]> wrote: > Isn't Nightly exactly the channel for trying out new configurations? What > is our stance on webcompat in Nightly? I had the impression website > breakage is acceptable on Nightly, especially given that this config will > reach release "soon". For folks who are testing with Nightly this is an > opportunity for them to spot breakage in their own applications. > > On Wed, 26 Aug 2026 at 17:57, 'Jeff Muizelaar' via > [email protected] <[email protected]> wrote: > >> Are we running an origin trial? >> >> Chrome's current disablement has presumably helped them build a list of >> origins currently broken with XSLT disabled. If we disable on Nightly, all >> of those sites will be broken and we'll have to discover them ourselves. If >> we can't get the list of sites that Chrome has left XSLT enabled, disabling >> it on Nightly has a clear webcompat cost and offers limited advantage. >> >> So my suggestion is: >> 1. Copy the list of origins that Chrome has XSLT enabled and leave it >> enabled for those origins on Nightly >> or >> 2. Don't disable on Nightly until Chrome's origin trial has ended (Aug >> 30, 2027) >> >> -Jeff >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" 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/mozilla.org/d/msgid/dev-platform/CAKb2zs9-DiCXjY6%2BbH1-VoE6_p0E12UEi2mmD%3DKeD1-qw72EaQ%40mail.gmail.com >> <https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAKb2zs9-DiCXjY6%2BbH1-VoE6_p0E12UEi2mmD%3DKeD1-qw72EaQ%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups " > [email protected]" 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/mozilla.org/d/msgid/dev-platform/CAPdF9uPO537cJ%3D7HFW8A4GtR9rL%2BaSP-EQVfhyTVn%3D-knZWOOw%40mail.gmail.com > <https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CAPdF9uPO537cJ%3D7HFW8A4GtR9rL%2BaSP-EQVfhyTVn%3D-knZWOOw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Simon Pieters https://www.mozilla.com/ -- You received this message because you are subscribed to the Google Groups "[email protected]" 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/mozilla.org/d/msgid/dev-platform/CAC7mYC4dZAHVCjD6CoqpiiqDVds56VR%3DPf79MSkmfs_VnYQ0Qg%40mail.gmail.com.
