If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

clone chrome's expanded reload options in Dev Edition

NEW
Unassigned

Status

()

Firefox
Developer Tools
3 years ago
2 years ago

People

(Reporter: canuckistani, Unassigned)

Tracking

36 Branch
x86
Mac OS X
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

See addy's tweet:

https://twitter.com/addyosmani/status/563130061231235072

That's bad-ass, we should do it.

In Firefox, this is what I get instead:

http://note.io/1zSRd7E
I generally deal with cache stuff so I can take a look.
Assignee: nobody → mratcliffe
No time.

Filter on 1ff0543e-b501-4893-a72b-e4773c01e655
Assignee: mratcliffe → nobody
Duplicate of this bug: 1176416
Created attachment 8625639 [details]
chrome-hard-refresh-options.png

Comment from Bug 1176416:

Chrome 42+ has a feature (when dev tools is open) in which pressing and holding the reload button in the location bar opens a contextual dropdown with three options:

-Normal reload
-Hard reload
-Empty cache and hard reload

Screenshot attached.

This is extremely useful for clearing cache repeatedly during development, and also for power users who need to confirm that they are getting the latest version of a file. Please consider implementing something similar.
Comment from Bug 1176416:

This feature seems really handy.  A little weird that it only happens when the toolbox is opened, but I guess that is to keep non-devs from seeing it (it's not clear to me if that would actually be a bad thing).

We already have a hold-to-open menu UI on the back/forward buttons, so maybe some of that could be reused.
You need to log in before you can comment on or make changes to this bug.