Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose AbortSignal.timeout on all globals #1253

Closed

Conversation

ptomato
Copy link

@ptomato ptomato commented Feb 7, 2024

Delete the Exposed attribute from AbortSignal.timeout, letting it inherit [Exposed=*] from AbortSignal.

Cf. whatwg/html#9893 where other timers are being exposed in ShadowRealm global contexts.

  • At least two implementers are interested (and none opposed):
    • T.B.D.
  • Tests are written and can be reviewed and commented upon at:
    • T.B.D.
  • Implementation bugs are filed:
    • Chromium: T.B.D.
    • Gecko: T.B.D.
    • WebKit: T.B.D.
    • Deno (only for aborting and events): T.B.D.
    • Node.js (only for aborting and events): T.B.D.
  • MDN issue is filed: T.B.D.
  • The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)


Preview | Diff

Delete the Exposed attribute from AbortSignal.timeout, letting it
inherit [Exposed=*] from AbortSignal.

Cf. whatwg/html#9893 where other timers are
being exposed in ShadowRealm global contexts.
@ptomato
Copy link
Author

ptomato commented Feb 29, 2024

Given the discussion in tc39/proposal-shadowrealm#398, let's close this for now.

@ptomato ptomato closed this Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant