Internal PR165119 When DefaultTapHighlight hide() happens, it adds the fade animation to the overlay. However, it doesn't remove the animation until the next draw() call, which happens when the user touches another link. In between those two events, the animation is still part of m_runningAnimations in LayerCompositingThread, so it continuously requesting frames from AnimationFrameRateController in the WebPageCompositor. This results in much lower frame-rates when you go to http://www.craftymind.com/guimark3/ and click the link for the bitmap test. Going to the test without clicking a link & triggering the animation results in much faster frame-rates: http://www.craftymind.com/factory/guimark3/bitmap/GM3_JS_Bitmap.html You can also verify by enabling AFRC logging and checking that if the user touches one link, frames are requested continuously after, except when the user touches another link but hasn't released yet.
Created attachment 148354 [details] Patch
Comment on attachment 148354 [details] Patch LGTM.
Comment on attachment 148354 [details] Patch Clearing flags on attachment: 148354 Committed r120734: <http://trac.webkit.org/changeset/120734>
All reviewed patches have been landed. Closing bug.