Don't send zeros in TexImage if GL implementation handles that
Created attachment 93011 [details] Patch
This fixes http://code.google.com/p/chromium/issues/detail?id=81474 .
I know this is chromium-only, but Simon might want to see this go by.
Comment on attachment 93011 [details] Patch If we're going to go down this route then it seems to me that we should just get rid of the texImage2DResourceSafe entry point and fold its functionality into texImage2D. We can rename the current GraphicsContext3D::texImage2D to texImage2DImpl. What do you think?
Sounds reasonable, but maybe other platforms don't always feel the need to fill a new texture with zeros. Say, if they know they're going to be filling it with TexSubImages later.
Comment on attachment 93011 [details] Patch OK, fair point. r=me
Comment on attachment 93011 [details] Patch Clearing flags on attachment: 93011 Committed r86275: <http://trac.webkit.org/changeset/86275>
All reviewed patches have been landed. Closing bug.