fetch/range/sw.https.window.js is validating that 216/416 range responses cannot be reused for non range requests.
As part of the test implementation, it uses a media element to generate various range responses that a service worker tries to reuse for non range requests.
The principle is sound but the current test expects specific range requests to be generated by the media engine. Safari media engine does not generate the range requests as expected by the test.
For that reason, the test times out in Safari.
#62313 is updating the test to move from a timeout to a failure, which is an improvement.
Ideally, the test would be rewritten so that it does not rely on specific media engine behaviour.
In the meantime, I wonder whether this test should be excluded from Interop 2026, since the test failure is unrelated for range request handling/range response validation.
fetch/range/sw.https.window.js is validating that 216/416 range responses cannot be reused for non range requests.
As part of the test implementation, it uses a media element to generate various range responses that a service worker tries to reuse for non range requests.
The principle is sound but the current test expects specific range requests to be generated by the media engine. Safari media engine does not generate the range requests as expected by the test.
For that reason, the test times out in Safari.
#62313 is updating the test to move from a timeout to a failure, which is an improvement.
Ideally, the test would be rewritten so that it does not rely on specific media engine behaviour.
In the meantime, I wonder whether this test should be excluded from Interop 2026, since the test failure is unrelated for range request handling/range response validation.