Web-Facing Change PSA: Reuse no-store images on same-src reassignment

[Helmut Januschka]

Contact emails

hjanu...@gmail.com

Specification

https://html.spec.whatwg.org/multipage/images.html#available-images

Summary

Allow same-document available-image reuse to bypass Cache-Control: no-store reload when the same src value is reassigned to an <img> element. Previously, Blink would re-fetch the image even though it was already decoded and available in the document. This aligns with existing Gecko and WebKit behavior.

Blink component

Blink>Loader

Web Feature ID

Missing feature

Motivation

Web interop fix. Chrome is the only browser failing the WPT for no-store image reuse on same-src reassignment. Filed by Mozilla.

Initial public proposal

No information provided

TAG review

No information provided

TAG review status

Not applicable

Risks

Interoperability and Compatibility

Low. Sites relying on img.src = img.src to force re-fetch of a no-store image returning different content on each request would no longer see the image update. Kill switch feature flag available.

Gecko: Shipped/Shipping

WebKit: Shipped/Shipping

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?

Yes
html/semantics/embedded-content/the-img-element/image-alternate-no-store.window.html

Flag name on about://flags

No information provided

Finch feature name

ReuseNoStoreImageOnSameSrcReassignment

Rollout plan

Will ship enabled for all users

Requires code in //chrome?

False

Tracking bug

https://crbug.com/486562295

Estimated milestones

Shipping on desktop
147
Shipping on Android
147
Shipping on WebView
147
Shipping on iOS
147

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/5206171399094272?gate=4728462755627008

This intent message was generated by Chrome Platform Status.

[Rick Byers]

Nice, thanks for the fix Helmut!

--
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 blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5e8d2fc9-604a-4dca-b242-031dfa075a84n%40chromium.org.