4 ms·

I have noticed a recent decline in the debugging features of FF -- downright buggy. View source shows a form I used 3 pages ago, not the form rendered. I now s

I have noticed a recent decline in the debugging features of FF -- downright buggy. View source shows a form I used 3 pages ago, not the form rendered. I now switch to chrome just for debugging.

foepys 6y ago
You don't deserve the downvotes. We are using mainly Firefox at work and sometimes, not often but sometimes, Firefox refuses to load the current file in the debugger. The only solution is to restart Firefox. I get why some are annoyed by this when they are in a debugging session. Although the last time it happened to me was one or two Firefox releases ago. Maybe it got fixed.
- hosteur 6y ago
  Did you report the problem?
  - foepys 6y ago
    No because I cannot reproduce it. It just happened randomly in the past. As I don't like getting bug reports that boil down to "doesn't work", I don't create them myself.
    - kevingadd 6y ago
      When struggling with a persistent issue like this in FF devtools it can still be worth filing an issue on the bugzilla tracker. Worst case, it gets closed as not reproducible. In practice many of these issues will eventually get caught if enough people complain about them and someone manages to dig through all the reports and come up with theories about the issue. You may get a helpful reply from someone on the team with suggestions on how to troubleshoot it, like enabling specific logging flags or pulling some info out of the console. I've filed lots of bug reports against Firefox in the past and just because you don't have an isolated reproduction case for a devtools issue, that doesn't mean it can't be fixed.
- tomashubelbauer 6y ago
  Try accessing the URL of the resource directly in its own tab and then restarting the tab where you're seeing the issue. That works for me.
- swimming_elwood 6y ago
  That's interesting. I have somewhat recently encountered the same thing with Chrome. I don't know what causes it but when it happens, the debugger hits and doesn't show me the context at all. But if I re-trigger the debugger again, it shows me everything just fine. :shrug:
- worble 6y ago
  I have a similar issue where very occasionally the debugger tab will just be empty, just absolutely no files in there at all. The fix is simple enough - just open the site in a new tab, although it's a little annoying. I still do all my development in Firefox regardless, I'm sure if I switched to Chrome I'd quickly discover a set of equally annoying bugs and quirks there too. Better the devil you know.
capitainenemo 6y ago
https://bugzilla.mozilla.org/show_bug.cgi?id=1685334 https://bugzilla.mozilla.org/show_bug.cgi?id=1685334 perhaps?
- eplanit 6y ago
  That describes it exactly -- thanks for finding that.

I have noticed a recent decline in the debugging features of FF -- downright buggy. View source shows a form I used 3 pages ago, not the form rendered. I now switch to chrome just for debugging.

foepys 6y ago

You don't deserve the downvotes. We are using mainly Firefox at work and sometimes, not often but sometimes, Firefox refuses to load the current file in the debugger. The only solution is to restart Firefox. I get why some are annoyed by this when they are in a debugging session. Although the last time it happened to me was one or two Firefox releases ago. Maybe it got fixed.

hosteur 6y ago
Did you report the problem?
- foepys 6y ago
  No because I cannot reproduce it. It just happened randomly in the past. As I don't like getting bug reports that boil down to "doesn't work", I don't create them myself.
  - kevingadd 6y ago
    When struggling with a persistent issue like this in FF devtools it can still be worth filing an issue on the bugzilla tracker. Worst case, it gets closed as not reproducible. In practice many of these issues will eventually get caught if enough people complain about them and someone manages to dig through all the reports and come up with theories about the issue. You may get a helpful reply from someone on the team with suggestions on how to troubleshoot it, like enabling specific logging flags or pulling some info out of the console. I've filed lots of bug reports against Firefox in the past and just because you don't have an isolated reproduction case for a devtools issue, that doesn't mean it can't be fixed.
tomashubelbauer 6y ago
Try accessing the URL of the resource directly in its own tab and then restarting the tab where you're seeing the issue. That works for me.
swimming_elwood 6y ago
That's interesting. I have somewhat recently encountered the same thing with Chrome. I don't know what causes it but when it happens, the debugger hits and doesn't show me the context at all. But if I re-trigger the debugger again, it shows me everything just fine. :shrug:
worble 6y ago
I have a similar issue where very occasionally the debugger tab will just be empty, just absolutely no files in there at all. The fix is simple enough - just open the site in a new tab, although it's a little annoying. I still do all my development in Firefox regardless, I'm sure if I switched to Chrome I'd quickly discover a set of equally annoying bugs and quirks there too. Better the devil you know.

capitainenemo 6y ago

https://bugzilla.mozilla.org/show_bug.cgi?id=1685334 https://bugzilla.mozilla.org/show_bug.cgi?id=1685334 perhaps?

eplanit 6y ago
That describes it exactly -- thanks for finding that.