4ef986db65
This stems from a behavior difference between Skia and Chrome. In Skia, we want to write transparent pixels as often as possible. (It's faster than checking if we should skip each pixel.) In Chrome, they avoid writing transparent pixels unless absolutely necessary. We were cautious about changing behavior when this first landed, but this is easier to think about in a smaller change (right now). (1) We can always write transparent pixels when we are writing an independent frame. (2) There is no need for the progressiveDisplay() check. We only ever use progressive display methods on the first frame - and the first frame is always independent. BUG=skia: GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=4379 Change-Id: I82048a08e2003aac216f483c7db8df997b687149 Reviewed-on: https://skia-review.googlesource.com/4379 Commit-Queue: Matt Sarett <msarett@google.com> Reviewed-by: Leon Scroggins <scroggo@google.com> |
||
---|---|---|
.. | ||
angle2 | ||
cpu-features | ||
dng_sdk | ||
etc1 | ||
expat | ||
freetype/include/freetype-android | ||
freetype2 | ||
gif | ||
harfbuzz | ||
icu | ||
jsoncpp | ||
ktx | ||
libjpeg-turbo | ||
libmicrohttpd | ||
libpng | ||
libsdl | ||
libwebp | ||
lua | ||
native_app_glue | ||
piex | ||
sfntly | ||
yasm | ||
zlib | ||
BUILD.gn | ||
README | ||
third_party.gni |
The third_party directory contains a set of dependencies from outside sources that are needed to build various components and tools within Skia. Some of these dependencies reside within the Skia repo, while others are pulled from other repositories and placed in the third_party/externals directory during build. These external dependencies are defined in a DEPS file. Products in third_party are subject to their own respective license terms. The license for each project should be included in the source itself via a license header or file. If the source itself does not include a license header or file, create a README that refers to reliable documentation of the project's license terms on the web.