🤖 Opened new upstream WPT pull request (web-platform-tests/wpt#50853) with upstreamable changes.

✍ Updated existing upstream WPT pull request (web-platform-tests/wpt#50853) title and body.

Rebasing should fix the test-tidy failure.

🛠 These changes could not be applied onto the latest upstream WPT. Servo's copy of the Web Platform Tests may be out of sync.

@delan @Loirooriol PTAL, thanks!

Looks like the DCO workflow has not started, for some reason. @xiaochengh can you try rebasing and doing a force push?

📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#50853).

Is it really okay to just remove size-adjust from the upstream wpt test?

This is modifying the reference file, so it doesn't use size-adjust property. The test still uses it. It's good to avoid using the same property in the reference file, as it can cause false passes like in this case.

Also with this change, the test is still passing in Chromium, Firefox and failing in Safari as before this change, see: https://github.com/web-platform-tests/wpt/pull/50853/checks?check_run_id=37595996561

No big deal, but I don't see the need to change the ref, it seems to make the test slightly more fragile in case that size-adjust: 1000% and font-size: 1000% were to behave slightly different on some browser/platform (not much familiar with size-adjust to know if it's possible). Not supporting a feature doesn't mean that absolutely all tests related to it must fail.

@Loirooriol size-adjust: 1000% is specified to work the same as font-size: 1000%. I wrote the spec :)