Skip to content

Breaking changes for 4.3 #991

Closed
Closed

Description

@orta

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 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.

Activity

  1. Stef-Gijsberts commented on Jun 19, 2021

    @Stef-Gijsberts

    (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".

  2. orta commented on Jun 20, 2021

    @orta
    ContributorAuthor

    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

  3. nainkunal933 commented on Aug 17, 2022

    @nainkunal933

    I would like to re-raise Stef Gijsberts (@Stef-Gijsberts) concern regarding RTCRtpEncodingParameters.maxFramerate being removed from 4.3. This is a breaking change for us as well. It seems like since this was last visited maxFramerate's support has increased.

    Orta Therox (@orta) is it possible to re-add maxFramerate if it passes the heuristics now?

  4. x-epoch commented on Oct 13, 2022

    @x-epoch

    I also would like to re-raise this issue since all browsers with latest version are support maxFramerate now, and it is real an import interface for webRTC video control.

  5. orta commented on Oct 13, 2022

    @orta
    ContributorAuthor

    If you followed the linked issue, you'd see that we're open to PRs for it, #1380 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions