RFC 242: Wide-gamut and HDR screenshot reftests - #242
Draft
Minju-kim-igalia wants to merge 2 commits into
Draft
Conversation
Minju-kim-igalia
changed the title
Update the RFC number for wide-gamut and HDR screenshot reftests.
Minju-kim-igalia
marked this pull request as draft
July 29, 2026 08:03
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 RFC proposes opt-in
reftest-color-spacemetadata for wide-gamut and HDR screenshot reftests.For opted-in tests,
wptrunnerrequests PNG output in the requested color space through WebDriver BiDi and compares the decoded samples without converting them to sRGB. The same request applies to the root test and its reference graph.The WebDriver BiDi protocol extension is tracked separately in w3c/webdriver-bidi#1114. The intended first end-to-end target is
display-p3/image/png.For implementation feasibility, I also uploaded a small Chromium WIP CL stack for that initial path:
The second CL depends on the first. These CLs are supporting feasibility prototypes rather than final landing proposals. The WebDriver BiDi contract and the upstream
chromium-bidiand WPT implementation changes remain separate work.Related: