5 ms·

I love all the work the Firefox team is doing here over the last year. Things have improved so much, its terrific. These are the things Firefox needs before I c

I love all the work the Firefox team is doing here over the last year. Things have improved so much, its terrific. These are the things Firefox needs before I could start to consider it as a primary development tool: - Performance analyzation - Resource management (cookies, local storage, etc) - Option to completely disable cache when dev tools are open - Ability to search the document in the inspector I'm sure they'll get there before too long.

Touche 13y ago
Already has an option to disable the cache. Advanced settings.
- tyleregeto 13y ago
  Thank you! Edit: I can't find it. I see I can disable the cache completely, but that's not really what I want. Its nice to only disable it when the dev tools are open. I don't want to have to go to advance settings and clear it every time.
  - Touche 13y ago
    Why specifically "when the dev tools are open"? That seems like an unusually specific request.
    - jordanlev 13y ago
      This is how Chrome DevTools do it (by default), and it's incredibly useful. When I'm just browsing websites I want the cache enabled, but when I'm working on a site (in which case I usually have the DevTools opened) I want the cache disabled. In fact, I now just open the DevTools when I want to temporarily disable caching -- because the keyboard shortcut is so ingrained it's a lot easier to do that then find the overall browser setting itself.
      - Touche 13y ago
        I know that's how Chrome DevTools does it, but "because that's how Chrome DevTools does it" is not a good answer to the question "why specifically when the DevTools are open".
        joesb 13y ago
        Because you don't want to disable caching of every other sites when you are not wearing your developer hat, just a "regular user surfing internet" hat.
        Touche 13y ago
        That's not how it works. It only disables the tab you are working in.
        jordanlev 13y ago
        This is exactly the point -- when you're developing a site, you want caching disabled on that site, but then when you're browsing another site just as a regular surfer you do not want caching disabled. Since generally when you're working on a site, you have DevTools opened, and generally when you're just browsing the web you do not have DevTools open, this is very nice.
        Touche 13y ago
        I disagree with this: > when you're developing a site, you want caching disabled on that site I don't know why you say that. I only want caching disabled if I'm debugging something I think might be caused by caching.
        extra88 13y ago
        Sounds like a case for using separate Firefox profiles, one for each "hat."
        13y ago
alexcroox 13y ago
I'm actually surprised developers using Firefox don't use firebug? It's great that Mozilla are improving the native tools but they are a long way from a moving goal post that is Firebug.

Touche 13y ago

Already has an option to disable the cache. Advanced settings.

tyleregeto 13y ago
Thank you! Edit: I can't find it. I see I can disable the cache completely, but that's not really what I want. Its nice to only disable it when the dev tools are open. I don't want to have to go to advance settings and clear it every time.
- Touche 13y ago
  Why specifically "when the dev tools are open"? That seems like an unusually specific request.
  - jordanlev 13y ago
    This is how Chrome DevTools do it (by default), and it's incredibly useful. When I'm just browsing websites I want the cache enabled, but when I'm working on a site (in which case I usually have the DevTools opened) I want the cache disabled. In fact, I now just open the DevTools when I want to temporarily disable caching -- because the keyboard shortcut is so ingrained it's a lot easier to do that then find the overall browser setting itself.
    - Touche 13y ago
      I know that's how Chrome DevTools does it, but "because that's how Chrome DevTools does it" is not a good answer to the question "why specifically when the DevTools are open".
      - joesb 13y ago
        Because you don't want to disable caching of every other sites when you are not wearing your developer hat, just a "regular user surfing internet" hat.
        Touche 13y ago
        That's not how it works. It only disables the tab you are working in.
        jordanlev 13y ago
        This is exactly the point -- when you're developing a site, you want caching disabled on that site, but then when you're browsing another site just as a regular surfer you do not want caching disabled. Since generally when you're working on a site, you have DevTools opened, and generally when you're just browsing the web you do not have DevTools open, this is very nice.
        Touche 13y ago
        I disagree with this: > when you're developing a site, you want caching disabled on that site I don't know why you say that. I only want caching disabled if I'm debugging something I think might be caused by caching.
        extra88 13y ago
        Sounds like a case for using separate Firefox profiles, one for each "hat."
        13y ago

alexcroox 13y ago

I'm actually surprised developers using Firefox don't use firebug? It's great that Mozilla are improving the native tools but they are a long way from a moving goal post that is Firebug.