Bug 227745 – Use setBooleanAttribute instead of setAttributeWithoutSynchronization(X, Y ? emptyAtom() : nullAtom());

• Status: RESOLVED
• Resolution: FIXED
• Component: DOM

[Tim Nguyen (:ntim)]

https://webkit-search.igalia.com/webkit/search?q=emptyAtom%28%29+%3A+nullAtom%28%29%29&path=&case=false&regexp=false

In these 2 cases, attribute sync doesn't really add value here. SetBooleanAttribute() is easier to read.

[Radar WebKit Bug Importer]

<rdar://problem/80269282>

[Radar WebKit Bug Importer]

<rdar://problem/80269369>

[Radar WebKit Bug Importer]

<rdar://problem/80269378>

[Tim Nguyen (:ntim)]

Created attachment 433030 [details]
Patch

[EWS]

Committed r279643 (239456@main): <https://commits.webkit.org/239456@main>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 433030 [details].

[Darin Adler]

Comment on attachment 433030 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=433030&action=review

> Source/WebCore/ChangeLog:8
> +        It's easier to read and attribute sync doesn't make a difference here (it only does for style & SVG attributes).

This comment shows a slight misunderstanding of "without synchronization". The function does not exist so that we can bypass synchronization. It’s an optimized case that saves work when we know the attribute we are setting is not something that can have SVG animation applied to it, nor is the attribute "style". By calling the plain old setAttribute, we are just forgoing a micro-optimization.

So a more accurate comment would be more like, "we can do without the slight optimization that we get by calling setAttributeWithoutSynchronization".