- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 May 2023 13:50:17 +0000
- To: public-css-archive@w3.org
Reading both #8561 and #8597, I see both ink-overflow and max-texture-size as implementation-defined things that shouldn't be web observable. So we'll have some notes that ink-overflow is applied to the canvas and some big elements might not be rendered as expected due to hardware constraints, but otherwise all of this is an implementation thing. This is not different from regular CSS transforms and accelerated compositing, where sometimes you have tiling artifacts or run out of texture memory. We can also treat those as bugs, and incrementally try our best to show something legible (e.g. a blurry scaled-down version of the texture, or use tiling) and vendors can differentiate on this if they want. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/8819#issuecomment-1538393453 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 8 May 2023 13:50:19 UTC