On Thu, Feb 19, 2026 at 10:51 PM TAMURA, Kent <[email protected]> wrote:
> > > On Fri, Feb 20, 2026 at 4:54 AM Chromestatus < > [email protected]> wrote: > >> *Contact emails* >> [email protected] >> >> *Specification* >> >> https://www.w3.org/TR/css-images/#ref-for-valdef-image-rendering-crisp-edges >> >> *Design docs* >> *No information provided* >> https://www.w3.org/TR/css-images/#valdef-image-rendering-crisp-edges >> >> https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/image-rendering#crisp-edges >> >> *Summary* >> "image-rendering: crisp-edges" indicates that image should be scaled in a >> way that preserves contrast and edges, and which avoids smoothing colors or >> introducing blur to the image in the process Note: spec wise this is >> technically different than 'pixelated'. In actual implementations it is >> not. Spec wise 'pixelated' = use any process the UA wants to make the >> result look pixelated. nearest-neighbor is acceptable. 'crisp-edges' = use >> any process you want that preserves contrast, edges, and avoids blending >> colors, nearest-neighbor is acceptable. Both Firefox and Safari use treat >> both as synonym and use nearest-neighbor for both. >> >> > So how does it work in Chromium? Is `crisp-edges` same as `pixelated` > like Firfox and Safari, or is it different from `pixelated`? > Yes, it's effectively a synonym for 'pixelated', same as Safari and Firefox > > >> *Blink component* >> Blink>CSS >> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> >> >> *Web Feature ID* >> image-rendering <https://webstatus.dev/features/image-rendering> >> >> *Motivation* >> *No information provided* >> >> *Initial public proposal* >> *No information provided* >> >> *Search tags* >> image-rendering <http:///features#tags:image-rendering>, crisp-edges >> <http:///features#tags:crisp-edges>, pixelated >> <http:///features#tags:pixelated> >> >> *TAG review* >> *No information provided* >> >> *TAG review status* >> Not applicable >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> image-rendering:crisp-edges support has been shipping in Safari since >> 2016 and Firefox since 2019 >> >> *Gecko*: Shipped/Shipping ( >> https://bugzilla.mozilla.org/show_bug.cgi?id=1496617) >> >> *WebKit*: Shipped/Shipping ( >> https://github.com/WebKit/WebKit/commit/31e3ae4099568fbdc594a95d9de4f7c226a8ded0 >> ) >> >> *Web developers*: No signals >> >> *Other signals*: >> >> *WebView application risks* >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> *No information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> Yes >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> Yes >> >> https://wpt.fyi/results/css/css-images/parsing/image-rendering-computed.html >> https://wpt.fyi/results/css/css-images/parsing/image-rendering-valid.html >> https://wpt.fyi/results/css/css-typed-om/the-stylepropertymap/properties/image-rendering.html >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> *No information provided* >> >> *Non-finch justification* >> *No information provided* >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://issues.chromium.org/issues/41073066 >> >> *Estimated milestones* >> Shipping on desktop 148 >> Shipping on Android 148 >> Shipping on WebView 148 >> >> *Anticipated spec changes* >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> *No information provided* >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/5172217778405376?gate=6536836396744704 >> >> > Please ask for reviews of Privacy, WP Security, Enterprise, Debuggability, > Testing. > Sure, I wrongly assumed, as a tiny change with no new functionality, just a synonym for an existing feature that's been shipping over 7 years in other browsers would be uncontroversial. My bad. > > >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69976a56.050a0220.18866f.02fd.GAE%40google.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69976a56.050a0220.18866f.02fd.GAE%40google.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > TAMURA Kent > Software Engineer, Google > > > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKZ%2BBNrEuKrjqoCE230DVQEa8%2BLou%2BP99UeN9Ri%3DGHZ20DBzsg%40mail.gmail.com.
