Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Breaking changes for 4.3
See original GitHub issueFor 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 the lib.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 and WebAuthentication.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
If you followed the linked issue, you’d see that we’re open to PRs for it, https://github.com/microsoft/TypeScript-DOM-lib-generator/issues/1380#issuecomment-1250255126
(I’m not sure where to mention this. If there is a better place, please let me know.)
I suspect the automation overreached. I think it removed
RTCRtpEncodingParameters.maxFramerate, which is supported in Safari. I think the reason it was removed is that at the time of checking, there was no known “Supported” status for any browser on the caniuse page. But just now, the status for Safari was set to “Supported”.It might be worth considering to adjust the automation, such that it does not remove a feature if its status for a major browser is “Unknown”.