Skip to content

Remove width as relevant mutation for image - #13033

Open
TimvdLippe wants to merge 1 commit into
whatwg:mainfrom
TimvdLippe:width-relevant-mutation
Open

TimvdLippe wants to merge 1 commit into
whatwg:mainfrom
TimvdLippe:width-relevant-mutation

Conversation

@TimvdLippe

@TimvdLippe TimvdLippe commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

An engine that implements this will start to cause
several tests to either flake or incorrectly pass: servo/servo@2e584db

Fixes #9371

(See WHATWG Working Mode: Changes for more details.)


/images.html ( diff )

An engine that implements this will start to cause
several tests to either flake or incorrectly pass:
servo/servo@2e584db

Fixes whatwg#9371
@TimvdLippe

Copy link
Copy Markdown
Contributor Author

@zcorpan Since you opened #9371 would Gecko be supportive of changing the spec here? When we implement it as-is, then Servo would have significant flakiness in two test suites.

@annevk

annevk commented Oct 3, 2026

Copy link
Copy Markdown
Member

If the main engines already do this, this doesn’t need explicit support. Might be good to mention that in the final commit message.

@TimvdLippe

Copy link
Copy Markdown
Contributor Author

Well, I am not confident to claim that. When I looked up the relevant tests, Gecko and Webkit might actually implement this: https://wpt.fyi/results/html/semantics/embedded-content/the-img-element/relevant-mutations-lazy.html?label=experimental&label=master&aligned

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

The width attribute should not be a relevant mutation

2 participants