location.reload() behavior change

Originally, location.reload() revalidates all cached resources. But from the m57, this behavior is changed to revalidate only the main resource, and to follow cache policy protocols for subresources.


https://groups.google.com/a/chromium.org/forum/#!topic/loading-dev/gD-MPRcfwVA/discussion The feature is enabled via server side configuration on Chrome m57. Without server managed configuration, chromium-based applications need to wait for m59 that enables the feature by default in the source code. E.g., probably Opera Starts supporting this at 46, and WebView does at m59.

Status in Chromium


Enabled by default (tracking bug) in:

  • Chrome for desktop release 57
  • Chrome for Android release 57
  • Android WebView release 59
  • Opera release 46
  • Opera for Android release 46

Consensus & Standardization

  • No public signals
  • No public signals
  • No public signals
  • No signals


Last updated on 2017-06-14