Add a new perf test to benchmark setting and reading CSS properties from JS.
Created attachment 131917 [details] Patch
Comment on attachment 131917 [details] Patch Attachment 131917 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/11952485 New failing tests: svg/repaint/repainting-after-animation-element-removal.svg
(In reply to comment #2) > (From update of attachment 131917 [details]) > Attachment 131917 [details] did not pass chromium-ews (chromium-xvfb): > Output: http://queues.webkit.org/results/11952485 > > New failing tests: > svg/repaint/repainting-after-animation-element-removal.svg oO really? Why so much hate EWS?
Comment on attachment 131917 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=131917&action=review > PerformanceTests/ChangeLog:11 > + * DOM/CSSPropertySetterGetter.html: Added. Maybe we should add PerformanceTests/CSSOM or PerformanceTests/CSS? > PerformanceTests/DOM/CSSPropertySetterGetter.html:1 > +<html> DOCTYPE? > PerformanceTests/DOM/CSSPropertySetterGetter.html:75 > + // We benchmark the property getter. This is self-evident. > PerformanceTests/DOM/CSSPropertySetterGetter.html:80 > + // We benchmark the property setter. Ditto.
Created attachment 131965 [details] Patch
Comment on attachment 131965 [details] Patch Clearing flags on attachment: 131965 Committed r110833: <http://trac.webkit.org/changeset/110833>
All reviewed patches have been landed. Closing bug.