This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

FF update 37 messed up net-tab in dev-tools

  • 4 replies
  • 1 has this problem
  • 3 views
  • Last reply by Tom

Tom
Tom
more options

Since the today update to 37 the net-tab in dev-tools is messed up and type-buttons are missing

i added a screenshot for clearification

system: Ubuntu Gnome 14.04.2 LTS 64-Bit FF: 37.0

Since the today update to 37 the net-tab in dev-tools is messed up and type-buttons are missing i added a screenshot for clearification system: Ubuntu Gnome 14.04.2 LTS 64-Bit FF: 37.0
Attached screenshots

Chosen solution

now with the new 38 version it works again, so something has had changed.

Read this answer in context 👍 0

All Replies (4)

Tom
Tom Question owner
more options

i tested arround and found out that in the vertical develeper view i can at least switch the visible type.

i add another screenshot to show what i mean

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
Tom
Tom Question owner
more options

since yesterday it worked as usual - today in the morning, there was an FF update (36 -> 37) and since then it stopped working - and now an extension should cause it?

thats like an an MS advice to reboot the PC...

anyways - i did what you suggested - and the problem stays - so that does not solve the issue.

Tom
Tom Question owner
more options

Chosen Solution

now with the new 38 version it works again, so something has had changed.