- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 Jan 2024 20:13:01 +0000
- To: public-css-archive@w3.org
@meyerweb wrote: > [removing default support for smart invert] does mean extra work for authors, but it’s work they should be doing anyway — and in many cases, will have to do even if the browser tries to guess which elements should be un-inverted, because it will inevitably guess wrong at some point. Why make millions of developers do extra work in order to serve the vast majority of users of this feature? Most authors will not, penalizing the users. - The defaults here get it right pf the vast majority of `<img>` usage on the web, without intervention needed by users or authors. - Authors can override it using the media feature in cases like the edge case listed above. - Users (on Apple platforms, an maybe more) can switch from Smart Invert to Classic Invert, which results in identical GPU inversion, but without any API for native or web apps to know it's "on." -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9674#issuecomment-1901044572 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 19 January 2024 20:13:03 UTC