Bug 219005
| Summary: | Implement ResizeObserver's devicePixelContentBox | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kenneth Russell <kbr> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Enhancement | CC: | apolostudioapps, cathiechen, cdumez, daxpedda, dino, fred.wang, gman, jdarpinian, karl+webkit, kkinnunen, koivisto, ricardovalero95, rik, simon.fraser, smoley, thorton, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: |
https://bugs.webkit.org/show_bug.cgi?id=230242 https://bugs.webkit.org/show_bug.cgi?id=291310 |
||
| Bug Depends on: | 157743 | ||
| Bug Blocks: | 244141 | ||
Kenneth Russell
ResizeObserver has gained the ability to observe the number of device pixels that a given element covers in the "device-pixel-content-box" observation:
https://www.w3.org/TR/resize-observer/#dom-resizeobserverboxoptions-device-pixel-content-box
This feature was discussed and specified in the CSS working group. Some concerns were raised by WebKit engineers at the time that WebKit can only provide an accurate answer for this observation after, and not before, the paint cycle runs. Even with this concern, this feature is important for web applications that expect to be able to do pixel-accurate rendering.
Now that WebKit has ResizeObserver support (thanks to Igalia folks for implementing it!), would it be possible to do at least a first-cut implementation of this new observation? It should make the example in the article https://web.dev/device-pixel-content-box/ render more stably. Currently it shows bad moiré effects in Safari Technology Preview on Retina display MacBook Pros.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/71469186>
Simon Fraser (smfr)
Some discussion that might result in spec changes here: https://github.com/w3c/csswg-drafts/issues/6608
Karl Dubost
*** Bug 264158 has been marked as a duplicate of this bug. ***
apolostudioapps
any news on this??