Skip to content

Conversation

@WeizhongX
Copy link
Contributor

Reverts #52556

Per Sam's comment:

With my WPT Core Team hat on, this change to testharness.js absolutely cannot land until whatwg/webidl#1465 does.

@gsnedders
Copy link
Member

tl;dr: we shouldn't be changing the behaviour of assert_throws_dom_impl based on unmerged PRs to specs, because this meaningfully changes the behaviour of every test in WPT.

@WeizhongX
Copy link
Contributor Author

Had a discussion in chromium. Maybe we want to revert chromium's change then wait that to be exported.

Let's hold on this for a while.

@domenic
Copy link
Member

domenic commented May 16, 2025

I mean, we're happy to land the Web IDL PR if that would make things easier, we just thought it'd be better to collect some compat data in Chromium first. But if that's going to cause us to be unable to test the changes, then maybe it's best to just merge it.

@Ms2ger Ms2ger merged commit 2f96fa1 into master May 16, 2025
24 of 26 checks passed
@Ms2ger Ms2ger deleted the revert-52556-chromium-export-3009dd8e45 branch May 16, 2025 09:48
aarongable pushed a commit to chromium/chromium that referenced this pull request May 21, 2025
This change updates services that use QuotaExceededError
to use the new DOMException derived QuotaExceededError class
when the flag is enabled.

I've not been allowed to update external wpts until the webidl
spec has been updated[0][1], so this change only updates tests for
Chrome only wpts, and otherwise updates expectations for
the external ones. External wpts will be updated when the
webidl spec is merged and I am allowed to update the external
wpts (as seen in chained CL).

[0] Spec PR: whatwg/webidl#1465
[1] Discussion: web-platform-tests/wpt#52571 (comment)

Bug: 406162261
Change-Id: Ie45d6095a3e4c21e21a35d2519d268580b8bc36b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6538066
Commit-Queue: Ayu Ishii <[email protected]>
Reviewed-by: Daseul Lee <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1463139}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants