Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Issue 600636 Change behavior of Reload to (validate main resource + regular load) instead of the current forced reload which triggers conditional requests on all the things
Starred by 5 users Project Member Reported by kenjibaheux@chromium.org, Apr 5 2016 Back to list
Status: Fixed
Owner:
Closed: Yesterday
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocked on:
issue 612701

Blocking:
issue 505048



Sign in to add a comment
We have too many reload behaviors...

Reload is used by users who want to see the latest content of a page. This means a regular load, like same URL navigation and pull to refresh (issue 558829) instead of a forced reload where we revalidate all the things (rather inefficient).


To be modified:
 - Simple click on the Reload button*
 - F5, Ctrl-R, Command-R
 - Reload option available from Reload's Context menu when DevTools is opened


*: on Android, the Reload button is the only option a user has to fix a broken page load. So, we might need to first provide a hard reload option before modifying its behavior. I'll open a different bug.



Not relevant for this bug (Hard reloads):
 - Ctrl/Shift + Click on the reload button
 - Ctrl+Shift+R, Command+Shift+R
 - Hard reload options available from Reload's Context menu when DevTools is opened


Since this touches UI, I'll reach out to the UX team.

 
Blocking: 505048
Blockedon: 599364
Blockedon: -599364
Status: Assigned
Summary: Change behavior of Reload to (validate main resource + regular load) instead of the current forced reload which triggers conditional requests on all the things (was: Change behavior of Reload to a normal load instead of the current forced reload which triggers conditional requests on all the things)
Similarly, updating summary to better reflect the desired behavior.
Comment 6 by bmau...@fb.com, Apr 25 2016
Labels: DevRel-Facebook
Blockedon: 612701
Labels: Reload
Hi, Kenji. How do we close this bug?

Now we shipped the new reload, and now location.reload() is consistent on the current stable channel.

Do you expect this bug also covers the mobile hard reload? Otherwise, I think we can close this now.
Comment 9 by kenjibaheux@chromium.org, Yesterday (24 hours ago)
Status: Fixed
Let's close this one since it was specific to the regular reload flows.
Sign in to add a comment