Bug 184496
| Summary: | CSSStyleDeclaration.setPropertyValue should always fire mutation records even if the declaration doesn't change. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Emilio Cobos Álvarez (:emilio) <emilio> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | bfulgham |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Emilio Cobos Álvarez (:emilio)
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Brent Fulgham
Safari 15.5+ passes the relevant cssom mutation tests.