When debugging over TextureMapper::ClipStack, I've noticed that the ClipStack::init() function is used not only when begin painting, but also when clearing. I'm used to see init() functions being called inside ctor's to initialize member variables that were unable to be assigned on an initialization list, which is not the case, and also because reset() better reflects the behavior (clears the clip stack and assigns a value to the initial clip state).
Created attachment 190106 [details] Patch Proposed patch
Comment on attachment 190106 [details] Patch Clearing flags on attachment: 190106 Committed r144003: <http://trac.webkit.org/changeset/144003>
All reviewed patches have been landed. Closing bug.