66742 2011-08-22 18:07:45 -0700 Write regression test for WebGL rate limiting 2024-01-17 01:23:10 -0800 1 1 1 Unclassified WebKit WebGL 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED P3 Enhancement --- 1 jbates webkit-unassigned darin kbr kkinnunen nduca oldest_to_newest 455126 0 jbates 2011-08-22 18:07:45 -0700 Write regression test for bug fix: https://bugs.webkit.org/show_bug.cgi?id=66445. This would test whether the WebGL rate limiting is properly executing. We would want to test both RAF and non-RAF use cases. In non-RAF cases, test that rate limiting kicks in only when it is supposed to. 455143 1 kbr 2011-08-22 18:46:37 -0700 I've changed the component to WebGL so that it shows up easily on searches. 459815 2 nduca 2011-08-31 12:06:48 -0700 There really are two things to veirfy here: that WebGLLayerChromium behaves correctly when dirtied outside of RAF, and that WebGLGraphicsContexts call setLayerUpdated. At least for the latter case, mock testing might be a more appropriate vehicle for testing. Mock could be: instantiate a compositor tree with a WebGLLayerChromium. Fire commands onto the webglcontext outside of the render task and assert that the ratelimiting task gets called on that context. 481893 3 nduca 2011-10-11 14:02:44 -0700 Might be good use case of frame rate tests on chromium-side.