-
Notifications
You must be signed in to change notification settings - Fork 431
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
Breaking changes for 4.3 #991
Comments
(I'm not sure where to mention this. If there is a better place, please let me I suspect the automation overreached. I think it removed It might be worth considering to adjust the automation, such that it does not |
If we were to re-add, it wouldn't pass our heuristics which is at least two popular browser support it: https://github.com/microsoft/TypeScript-DOM-lib-generator#what-are-the-typescript-teams-heuristics-for-prs-to-the-dom-apis So I think this was still right |
I would like to re-raise @Stef-Gijsberts concern regarding @orta is it possible to re-add |
I also would like to re-raise this issue since all browsers with latest version are support |
If you followed the linked issue, you'd see that we're open to PRs for it, #1380 (comment) |
For 4.3, we used the Mozilla browser-compat-data to remove types and features which are not used in any browser.
We base the
lib.dom.d.ts
on the specifications from W3C and WHATWG. These specifications are like all projects, and have some cruft on them over time. Now, we check the data powering caniuse.com to see if there are any implementations of a specification before including the types from that spec in thelib.dom.d.ts
.This is automated and running across a lot of specifications, so there's a possibility it has some overreach and we're open to bringing some back if we missed a common case. Some of the types removed:
Account
(this is now free to use in your own apps 🎉),AssertionOptions
,RTCStatsEventInit
,MSGestureEvent
,DeviceLightEvent
,MSPointerEvent
,ServiceWorkerMessageEvent
andWebAuthentication
.The text was updated successfully, but these errors were encountered: