Hi Liang,

https://chromestatus.com/metrics/feature/timeline/popularity/5356 is
already somewhat high, but it is also an upper bound on the risk and
probably not reflective of how many sites will be broken. Looking at a
sample of sites that hit the use counter and seeing what the impact of the
change is would be very helpful. If this isn't urgent, you could wait until
there are example sites listed on chromestatus.com, or get a list of sites
from Edge's UKM data. With a list of sites, checking ~20 of them at random
and reporting your findings should be enough to make a call on this.

Also, does the new behavior (returning a Worker object and later firing an
error event on it) already happen for some other kind of error, so that
it's likely already handled? That would also reduce the risk here.

Best regards,
Philip

On Tue, May 6, 2025 at 1:34 AM lzhao via Chromestatus <
admin+lz...@cr-status.appspotmail.com> wrote:

> Added telemetry data as siggested for the scenario and data can be viewed
> at https://chromestatus.com/metrics/feature/timeline/popularity/5356.
> There are some hits, but no hits for top sites. And Safari has also shipped
> the behavior change.
>
> --
> 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 blink-dev+unsubscr...@chromium.org.
> To view this discussion visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68194b11.170a0220.4750a.00de.GAE%40google.com
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68194b11.170a0220.4750a.00de.GAE%40google.com?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 blink-dev+unsubscr...@chromium.org.
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYfL6jkWjF3s%3DX1Ysz%2B1pQvzNgds5gkxTid3OKEe82P4%3DA%40mail.gmail.com.

Reply via email to