Reoptimize free-standing :focus/link/visited/-webkit-any-link selectors.
Created attachment 200532 [details] Patch
Comment on attachment 200532 [details] Patch Attachment 200532 [details] did not pass mac-wk2-ews (mac-wk2): Output: http://webkit-queues.appspot.com/results/332820 New failing tests: mathml/presentation/fractions.xhtml mathml/presentation/mo.xhtml mathml/presentation/mo-stretch.html mathml/presentation/attributes.xhtml mathml/presentation/row-alignment.xhtml mathml/presentation/subsup.xhtml mathml/presentation/fractions-vertical-alignment.xhtml mathml/presentation/over.xhtml fast/frames/crash-remove-iframe-during-object-beforeload.html mathml/presentation/roots.xhtml mathml/presentation/underover.xhtml
Created attachment 200535 [details] Archive of layout-test-results from webkit-ews-11 for mac-mountainlion-wk2 The attached test failures were seen while running run-webkit-tests on the mac-wk2-ews. Bot: webkit-ews-11 Port: mac-mountainlion-wk2 Platform: Mac OS X 10.8.2
Comment on attachment 200532 [details] Patch MathML why.
Created attachment 201255 [details] how about this?
Comment on attachment 201255 [details] how about this? Is there some good way to regression-test this so people don’t break it again? I know it can be hard to regression-test performance changes.
(In reply to comment #6) > (From update of attachment 201255 [details]) > Is there some good way to regression-test this so people don’t break it again? I know it can be hard to regression-test performance changes. I think this might even show up as progression in our regular tests. The change that broke this was a significant progression in itself and probably masked away the regression. We could definitely use better testing for things like this. Maybe debug only Internal API to record exact optimisations used?
http://trac.webkit.org/changeset/149838