You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
libdom.d.ts changes of 4.4.x break WebRTC standard #46379
I tried to follow all those topics about the libdom.d.ts changes introduced in 4.4.x but i did miss a topic that encapsulates that the changes totally break the WebRTC standard.
The changes are so massive that it takes some time to nail down what really is element of the current standard and what has been removed replaced improved.
to me this looks like some legacy Edge IDL definitions were removed. Some of the names are shared between WebRTC and ORTC which seems to be the main cause here.
The changes that affect us were introduced in 4.4.x with a merge by Daniel Rosenwasser (@DanielRosenwasser) so even if the origin of the sources is a second library i need to mention that here (at least to have all other affected notified properly)
The problem is that the change is breaking a widely used standard....
I do actually also wonder that no one was complaining about this standard breaking in total so far, maybe i am missing something.
The DOM lib generator creates these .d.ts files directly from the spec pages and then uses tools like the db powering caniuse to determine if the API is used in more than one browser, and W3C systems for declaring deprecations. The 4.4 changes should be very closely aligned with the spec for WebRTC. It's likely that the API changes which affected you are either:
The name of an interface being renamed in the spec (and thus in the .d.ts)
There being only one browser enginer implementing the API and thus not passing the bar for inclusion
The W3C declared something as unimplemented (which I guess won't be the case here)
If you think we've missed something we're happy to take issues on the specifics in the linked repo 👍🏻
The file itself has no reference in it - would actually prefer if the file would contain the information that it has been:
-- automatically created
-- by another repo (link)
-- and this was the version of that repo when the stub was created)
This issue has been marked as 'Question' and has seen no recent activity. It has been automatically closed for house-keeping purposes. If you're still waiting on a response, questions are usually better suited to stackoverflow or the TypeScript Discord community.
Activity
fippo commentedon Oct 15, 2021
to me this looks like some legacy Edge IDL definitions were removed. Some of the names are shared between WebRTC and ORTC which seems to be the main cause here.
MartinJohns commentedon Oct 15, 2021
This is the wrong repository for DOM related changes. You're looking for: https://github.com/microsoft/TypeScript-DOM-lib-generator
JanFellner commentedon Oct 15, 2021
Martin Johns (@MartinJohns) can you give me a wider picture?
The changes that affect us were introduced in 4.4.x with a merge by Daniel Rosenwasser (@DanielRosenwasser) so even if the origin of the sources is a second library i need to mention that here (at least to have all other affected notified properly)
Whats your proposal. Just open a ticket in the second library and link them together?
Just add the issue to microsoft/TypeScript-DOM-lib-generator#1029
The problem is that the change is breaking a widely used standard....
I do actually also wonder that no one was complaining about this standard breaking in total so far, maybe i am missing something.
orta commentedon Oct 15, 2021
The DOM lib generator creates these .d.ts files directly from the spec pages and then uses tools like the db powering caniuse to determine if the API is used in more than one browser, and W3C systems for declaring deprecations. The 4.4 changes should be very closely aligned with the spec for WebRTC. It's likely that the API changes which affected you are either:
If you think we've missed something we're happy to take issues on the specifics in the linked repo 👍🏻
JanFellner commentedon Oct 20, 2021
Can someone guide me a bite more to understand that process (or point me to where it is described?)
-- automatically created
-- by another repo (link)
-- and this was the version of that repo when the stub was created)
orta commentedon Oct 20, 2021
The version table is in the README for https://github.com/microsoft/TypeScript-DOM-lib-generator - adding the version metadata into the file is a great idea I've added it to that repo microsoft/TypeScript-DOM-lib-generator#1181
typescript-bot commentedon Oct 22, 2021
This issue has been marked as 'Question' and has seen no recent activity. It has been automatically closed for house-keeping purposes. If you're still waiting on a response, questions are usually better suited to stackoverflow or the TypeScript Discord community.