On Wed, Aug 26, 2026 at 5:57 PM '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. > I think the idea is to send a signal that we're serious about removing support, and give developers enough time to address any XSLT usage. I'm not sure if removing support in Nightly will sufficiently reach developers, though. Maybe a user-visible message at the top of the page (for all users) is more effective? (Chrome now has such a message.) > > So my suggestion is: > 1. Copy the list of origins that Chrome has XSLT enabled and leave it > enabled for those origins on Nightly > We can do this (for origins we can find in httparchive), but not until some time after November 17 (e.g. in Q1 2027). > or > 2. Don't disable on Nightly until Chrome's origin trial has ended (Aug 30, > 2027) > IMO we can be slightly more aggressive than this, but I agree we should generally avoid having an extended period of time of broken sites in Nightly while they continue to work in Chrome (due to origin trial or other). cheers, -- 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/CAC7mYC5HU_dr5eYJKz%2BikWFn%2BJMx%3DyFnVrVmgbB__gOxUt4p%3DA%40mail.gmail.com.
