Bug 287265
| Summary: | [HDR] Separate "is showing HDR" from screenContentsFormat() | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Said Abou-Hallawa <sabouhallawa> |
| Component: | Images | Assignee: | Said Abou-Hallawa <sabouhallawa> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | sabouhallawa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 282299 | ||
Said Abou-Hallawa
This function is a little confusing. It returns the best screen ContentsFormat for a given optional layer. I think the right design for this is
1. screenContentsFormat() should renamed screenContentsFormats() and it should return OptionSet<ContentsFormat>. The screen is capable of supporting multiple ContentsFormat. The layer should picks whatever suits it.
2. A new static function is added called PlatformCALayer::contentsFormatForLayer(). It will return the best screen ContentsFormat for a given optional layer. This function will call screenContentsFormats() and it will checks whether the PlatformCALayerClient wants to show HDR or not. If it does and the screen support RGBA16F, it will return RGBA16F.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/144396500>
Said Abou-Hallawa
Pull request: https://github.com/WebKit/WebKit/pull/40225
EWS
Committed 290069@main (01e5e2df42c3): <https://commits.webkit.org/290069@main>
Reviewed commits have been landed. Closing PR #40225 and removing active labels.