Update comments regarding image caching
While attempting to remove the layoutObject parameter the following observations were made: * The decoding forced by BitmapImage::imageForCurrentFrame will be deferred so the comment in the header may be removed. * BitmapImage::currentFrameKnownToBeOpaque() conservatively returns false for uncached images, not true. * Since decoding is deferred, there is no guarantee that the opaqueness metadata is available after the imageForCurrentFrame call has returned. It may increase the chance though, depending on image decoder for the particular image. NOTRY=true BUG=559131 Review URL: https://codereview.chromium.org/1454373005 Cr-Commit-Position: refs/heads/master@{#361094}
Showing
Please register or sign in to comment