-
Notifications
You must be signed in to change notification settings - Fork 12.8k
DOM update 2024-07-12 #59259
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
DOM update 2024-07-12 #59259
Conversation
I'm doing this early in preparation for adding `/** @deferred */` comments on callbacks for 5.6.
@typescript-bot test this |
@typescript-bot test it |
/** | ||
* Sets or retrieves a value that you can use to implement your own label functionality for the object. | ||
* | ||
* [MDN Reference](https://developer.mozilla.org/docs/Web/API/HTMLOptGroupElement/label) | ||
*/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did so many props lose their MDN links?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They probably have done page cleanup, and for example this link is now 404 (or has always been). Found this relevant PR mdn/browser-compat-data#23481
Hey @sandersn, the results of running the DT tests are ready. There were interesting changes: Branch only errors:Package: dom-view-transitions
Package: chrome-apps
Package: node/v16
Package: node/v18
|
@sandersn Here are the results of running the user tests with tsc comparing Something interesting changed - please have a look. Details
|
This is scary:
|
@sandersn Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@sandersn Here are the results of running the top 400 repos with tsc comparing Something interesting changed - please have a look. Details
|
This PR adds ImportMeta.resolve as a non-optional method: interface ImportMeta {
url: string;
resolve(specifier: string): string;
} But |
After discussing with @andrewbranch we decided to make ImportMeta.resolve required in node 16 and 18 as well. Forcing a null check before usage isn't the right way to handle experimental features in the first place. I'd prefer to delete The correct way would have been to have a separate experimental package, probably. |
DefinitelyTyped/DefinitelyTyped#70054 is merged now, so I'm going to merge this after resolving the baseline conflict. |
This is consistent with both the API: https://developer.mozilla.org/en-US/docs/Web/API/Element/requestPointerLock#return_value As well as its upcoming inclusion in TypeScript's built-in types for requestPointerLock: https://github.com/microsoft/TypeScript/blob/90da3ca5dd694f7029b535ea09727be899854d40/src/lib/dom.generated.d.ts#L7873 Which was added here: microsoft/TypeScript#59259
Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…6994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…e.d.ts (#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
…m#126994) Upgrade @types/node to work around an issue in TypeScript [1] that caused our "publish to VSCode Marketplace" github action [2] to fail: ``` node_modules/@types/node/module.d.ts:290:13 - error TS2386: Overload signatures must all be optional or required. 290 resolve?(specified: string, parent?: string | URL): Promise<string>; ``` [1] microsoft/TypeScript#59259 (comment) [2] https://github.com/llvm/vscode-lldb/actions/runs/13298213337/job/37134713009
I'm doing this early in preparation for adding
/** @deferred */
comments on callbacks for 5.6.Changes:
string | URL
Test baseline changes: