ParentNode.replaceChildren is excluded, but it's not clear to me why #985
Comments
|
cc @saschanaz Nicer GUI for the compat data: Support came june, september and october 2020 to the browsers. |
|
It wasn't widely available back in 2020. We can now remove the exclusion. |
This was referenced May 3, 2021
|
As in #1008 (comment), this is fixed. @github-actions close |
|
@github-actions close |
|
Closing because @saschanaz is one of the code-owners of this repository. |
kidonng
added a commit
to kidonng/refined-github
that referenced
this issue
Sep 30, 2021
Fix missing `ParentNode.replaceChildren` type, see microsoft/TypeScript-DOM-lib-generator#985
krassowski
added a commit
to krassowski/jupyterlab-limit-output
that referenced
this issue
Mar 24, 2023
see microsoft/TypeScript-DOM-lib-generator#985 which requires an update to a newer version of TypeScript (currently pinned at 4.1.3)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that the method
replaceChildrenon the interfaceParentNodehas explicitly been excluded. It's not clear to me why this is; as far as I can tell it's stable and present in most browsers. This change was introduced in a seemingly unrelated pull-request, which doesn't provide any hints as to why this was done. Is there a reason for this? Was this an accident?The text was updated successfully, but these errors were encountered: