There is a regression on NTP page reload after the reload behavior change.
Backgrounds:
- Chrome uses URLDataSource to return response for internal resources, e.g. chrome-search://local-ntp/config.js, and data URLDataSource returns allows caching by default.
- Some resources are dynamically created and could be different on each load, or reload.
- On reload, only the main resource is forcibly revalidated after the reload behavior changes.
Results:
- Chrome load sub-resources from memory cache, and could not reflect configuration changes
See crbug.com/668454 for actual regression issue.
Comment 1 by toyoshim@chromium.org
, Nov 30 2016