Split unoptimized-images feature policy into 3 policies. #15847
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wpt-pr-bot
approved these changes
Mar 14, 2019
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-1524869
branch
6 times, most recently
from
3fbe32c
to
190180b
Compare
This policy is split to enforce lossy versus lossless image types separately. Also, the lossless policy will currently have two forms, with with 1kB overhead and one with 10kB overhead allowed for each image. For now, the WebP image type will be enforced by the lossless policy, even though it is capable of lossy compression as well. Bug: 942659 Change-Id: I3221fcabd5c8bd5aaa2d0c2ecf845c3a2b5ccd78
chromium-wpt-export-bot
force-pushed
the
chromium-export-cl-1524869
branch
from
190180b
to
631670e
Compare
|
Close this PR because the Chromium CL has been abandoned. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This policy is split to enforce lossy versus lossless image types
separately. Also, the lossless policy will currently have two forms,
with with 1kB overhead and one with 10kB overhead allowed for each
image.
For now, the WebP image type will be enforced by the lossless policy,
even though it is capable of lossy compression as well.
Bug: 942659
Change-Id: I3221fcabd5c8bd5aaa2d0c2ecf845c3a2b5ccd78
Reviewed-on: https://chromium-review.googlesource.com/1524869
WPT-Export-Revision: fb2509bad4887aff803a32a49c1a6adbd6a95d1c