On Wed, Oct 29, 2025 at 8:42 AM Chris Harrelson <[email protected]>
wrote:

> LGTM2 for the steps Vlad mentioned.
>
> On Wed, Oct 29, 2025 at 8:38 AM Vladimir Levin <[email protected]>
> wrote:
>
>> Generally, we're supportive of removing XSLT. As for the plan, I think it
>> would be best if we disable this in Canary as soon as possible (via Finch)
>> to find real breakages that we may be missing. Further, disabling in Beta
>> and Dev shortly after to get more data is also good.
>>
>> LGTM1 for the plan with the above changes. We would like you to check in
>> with results of Canary / Dev / Beta and warning steps in 3 months to see
>> how we proceed further.
>>
>
Yep, that makes sense. I was planning to do that later in the process (M148
in my plan) but I like the idea of doing it ASAP - will do. I missed the
M143 branch, and I think to do that responsibly I'd want to include a
customized console message for the pre-stable channels. So I'll get that
landed in M144, and report back here after it goes through the channels.

Thanks,
Mason


> Thanks,
>> Vlad
>>
>> On Monday, October 27, 2025 at 9:37:51 AM UTC-4 j.j. wrote:
>>
>>>
>>>
>>> see also
>>> https://github.com/mozilla/standards-positions/issues/1287
>>>
>> --
>> 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/4aa38aaf-702e-41d6-91f1-7ba8b18ff675n%40chromium.org
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4aa38aaf-702e-41d6-91f1-7ba8b18ff675n%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/CAM%3DNeDjG95YROLAJVv-vPwqDtFhmBGwo_kwvEf%3Dc_iTOZxbgdA%40mail.gmail.com.

Reply via email to