- From: Andrew Sutherland <notifications@github.com>
- Date: Thu, 23 Jan 2025 09:04:10 -0800
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 23 January 2025 17:04:14 UTC
For Firefox/Gecko a specific limit is fine and even desirable given the inherent resource utilization and latency trade-offs for ServiceWorker registrations since handle fetch is on the critical path for page loads. That said, it probably would be good for any WPTs validating the limit to be structured to have both "impl works with values at the limit" and "impl throws for values exceeding the limit". (The [chromium test currently only does the latter right now](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/wpt_internal/service-worker/static-router/static-router-invalid-depth-width.https.html).) -- Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1746#issuecomment-2610433784 You are receiving this because you are subscribed to this thread. Message ID: <w3c/ServiceWorker/issues/1746/2610433784@github.com>
Received on Thursday, 23 January 2025 17:04:14 UTC