Skip to content

Unexpected Safari-specific event init options #1689

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.

Sign up for GitHub

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

Jump to bottom
Closed
turansky opened this issue Feb 12, 2024 · 3 comments · Fixed by #1964
Closed

Unexpected Safari-specific event init options #1689

turansky opened this issue Feb 12, 2024 · 3 comments · Fixed by #1964

Comments

@turansky
Copy link

  1. RTCPeerConnectionIceEventInit.url - Safari 12+ only
  2. FetchEventInit.replacesClientId - already removed form Safari
@Bashamega
Copy link
Contributor

Hello @turansky,
These options were removed from TypeScript a long time ago. Please try using the latest version of TypeScript.

@turansky
Copy link
Author

turansky commented Apr 2, 2025

@Bashamega it's still here:

  1. https://github.com/microsoft/TypeScript-DOM-lib-generator/blob/4a6d7cb3c0a2893eb08145d7c0d28fc9b9575a41/baselines/dom.generated.d.ts#L1767

  2. TypeScript-DOM-lib-generator/baselines/serviceworker.generated.d.ts

    Line 231 in 4a6d7cb

    replacesClientId?: string;

@Bashamega
Copy link
Contributor

Weird, I will open a PR for I today.

@Bashamega Bashamega mentioned this issue Apr 2, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Unexpected Safari-specific event init options Bashamega/TypeScript-DOM-lib-generator
2 participants
@turansky @Bashamega