{aborted: false} is treated as valid AbortSignal but not in other runtimes

[xwan99]

Version

v22.8.0

Platform

N/A

Subsystem

abort controller

What steps will reproduce the bug?

AbortSignal.any([ { aborted: false }])

How often does it reproduce? Is there a required condition?

100%

What is the expected behavior? Why is that the expected behavior?

Fail with TypeError

What do you see instead?

Passed

Additional information

This fails in other runtime like Chrome and Firefox

[RedYetiDev]

Spec: https://dom.spec.whatwg.org/#create-a-dependent-abort-signal

[RedYetiDev]

Can you provide the exact error given by other runtimes?

[xwan99]

In Firefox:

>> AbortSignal.any([ { aborted: false }])
Uncaught TypeError: AbortSignal.any: Element of argument 1 does not implement interface AbortSignal.
    <anonymous> debugger eval code:1

In Chrome:

> AbortSignal.any([ { aborted: false }])

VM176:1 Uncaught TypeError: Failed to execute 'any' on 'AbortSignal': Failed to convert value to 'AbortSignal'.
    at <anonymous>:1:13

[benjamingr]

This was a deliberate design choice (to not brand check) in order to have better ecosystem compatibility.

Now that we've had AbortSignal for a few years it's fine to revisit