Bug 184496 - CSSStyleDeclaration.setPropertyValue should always fire mutation records even if the declaration doesn't change.
Summary: CSSStyleDeclaration.setPropertyValue should always fire mutation records even...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: CSS (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-11 06:53 PDT by Emilio Cobos Álvarez (:emilio)
Modified: 2022-07-15 13:57 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Emilio Cobos Álvarez (:emilio) 2018-04-11 06:53:15 PDT 
See the test in https://github.com/w3c/web-platform-tests/pull/10429.

https://drafts.csswg.org/cssom/#dom-cssstyledeclaration-setpropertyvalue always
ends up in https://drafts.csswg.org/cssom/#update-style-attribute-for (step 8),
which calls https://dom.spec.whatwg.org/#concept-element-attributes-set-value,
which does queue a mutation record even if the value doesn't change.

This is consistent with setAttribute("style", getAttribute("style")),
for example.
Comment 1 Brent Fulgham 2022-07-15 13:57:46 PDT 
Safari 15.5+ passes the relevant cssom mutation tests.