Closed Bug 710157 Opened 13 years ago Closed 7 years ago

GCLI needs a cache control command

Categories

(DevTools Graveyard :: Graphic Commandline and Toolbar, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: jwalker, Unassigned)

References

Details

(Whiteboard: [gclicommands])

> cache off [--thisSessionOnly] > cache on > cache clear memory|disk|all
Blocks: GCLI-12
No longer blocks: GCLI-FUTURE
Bug triage, filter on PEGASUS.
Target Milestone: --- → Firefox 12
Bug triage, filter on PEGASUS.
Priority: -- → P2
Bug triage, filter on PEGASUS.
Thinking about this some more, what I really want is: > cache off localhost And I don't need to separate the different types of cache. So 3 sub commands: > cache off <all|domain> > cache on <all|domain> > cache list But I guess that's harder?
Assignee: nobody → dcamp
No longer blocks: GCLI-12
Target Milestone: Firefox 12 → Firefox 13
Target Milestone: Firefox 13 → Firefox 14
Target Milestone: Firefox 14 → Firefox 15
Blocks: 745773
No longer blocks: 745773
Target Milestone: Firefox 15 → Firefox 16
Blocks: GCLICMD
Pinging all command bugs marked for FF16. Should we mark for 17? Perhaps we should ask who would find this useful.
Filter on teabags
Whiteboard: [gclicommands]
Target Milestone: Firefox 16 → Firefox 17
Triage: Filter on the TRIAGE keyword.
Target Milestone: Firefox 17 → Future
New component triage. Filter on "Lobster Thermidor aux crevettes with a Mornay sauce"
Component: Developer Tools: Console → Developer Tools: Graphic Commandline and Toolbar
Assignee: dcamp → nobody
Resetting priorities because these P* levels are very out of date. Sorry for the bug spam. Filter on Lobster Thermidor
Priority: P2 → --
This isn't a particularly useful bug to have on file. It's a feature request, and we're not actively developing GCLI now, and are unlikely to in the forseeable future Closing
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.