Skip to content

Update @webref/idl to version 3.82.1 - #2535

Open
Adam Naji (Bashamega) wants to merge 10 commits into
microsoft:mainfrom
Bashamega:feat/bump-idl
Open

Update @webref/idl to version 3.82.1#2535
Adam Naji (Bashamega) wants to merge 10 commits into
microsoft:mainfrom
Bashamega:feat/bump-idl

Conversation

@Bashamega

@Bashamega Adam Naji (Bashamega) commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Split #2495

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for the PR!

This section of the codebase is owned by Kagami Sascha Rosylight (@saschanaz) - if they write a comment saying "LGTM" then it will be merged.

Comment thread baselines/ts5.5/dom.generated.d.ts Outdated
declare var ProcessingInstruction: {
prototype: ProcessingInstruction;
new(): ProcessingInstruction;
new(target: string, data?: string): ProcessingInstruction;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not supported by anyone I believe, we'll have to also remove this in KDL.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have fixed it and added support for it in kdl

…s multiple TypeScript definition files and update related handling in patches.
Comment thread src/build/types.ts Outdated
optional?: boolean;
variadic?: boolean;
}
export type Param =

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you do it without changing types.ts? Patching should not change base types unless the type is already wrong.

…ting Param interface for improved flexibility in method signatures.
Comment thread src/build/patches.ts Outdated
) {
params.push(param.name);
} else {
params.push(param);

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's better, but still kinda sad. I wonder it would be better to somehow treat { name: "foo" } with no other fields as foo on prune() level. If that's possible then we won't need this workaround for any future array items either. Thoughts?

@Bashamega

Copy link
Copy Markdown
Contributor Author

I have improved the logic Kagami Sascha Rosylight (@saschanaz)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I'll need to double check other changes, but the logic patch looks really good 🙏🏻👍🏻🎉

Comment thread src/build/patches.ts Outdated
Object.keys(item).length === 1 &&
Object.prototype.hasOwnProperty.call(item, "name") &&
typeof (item as Record<string, unknown>).name === "string",
)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you extract this lambda in every() into a separate function so that it becomes obj.every(isObjectWithOnlyName) (name free to change)?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the learning, I have updated it

Introduced isObjectWithOnlyName function to streamline checks for objects with a single 'name' property. Updated convertForRemovals to utilize this new helper for improved readability and maintainability.
Comment thread inputfiles/patches/pointerevents.kdl Outdated
@@ -0,0 +1,5 @@
removals {
dictionary WheelEventInit {
member momentum // Blink only as of 2025-08

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2025 or 2026? 👀

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOL, this was a typo, updated

@saschanaz

Copy link
Copy Markdown
Contributor

Now about the compiler test failure.

--- FAIL: TestLocal (2.34s)
    --- FAIL: TestLocal/globalThisBlockscopedProperties.ts (0.02s)
        --- FAIL: TestLocal/globalThisBlockscopedProperties.ts/type (0.00s)
            baseline.go:79: the baseline file /home/runner/work/TypeScript-DOM-lib-generator/TypeScript-DOM-lib-generator/TypeScript/tsc/testdata/baselines/reference/conformance/globalThisBlockscopedProperties.types has changed. (Run `hereby baseline-accept` if the new baseline is correct.)
    --- FAIL: TestLocal/mappedTypeRecursiveInference.ts (0.15s)
        --- FAIL: TestLocal/mappedTypeRecursiveInference.ts/type (0.12s)
            baseline.go:79: the baseline file /home/runner/work/TypeScript-DOM-lib-generator/TypeScript-DOM-lib-generator/TypeScript/tsc/testdata/baselines/reference/compiler/mappedTypeRecursiveInference.types has changed. (Run `hereby baseline-accept` if the new baseline is correct.)

Jake Bailey (@jakebailey), this is the first time I've seen this test failing. I don't understand why it fails because no line change happened, and the test file looks very simple. what do we do? Ignore it?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants