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

Firefox 54 Inspector no longer able to pinpoint elements

  • 6 பதிலளிப்புகள்
  • 5 இந்த பிரச்னைகள் உள்ளது
  • 1 view
  • Last reply by greyhood

Hi everyone,

I'm having trouble using the inspector tool for Firefox 54.

• The problem is it no longer pinpoints elements as it once did previously.

• This requires you to select an element but it will only select the parent element, to find a specfic element within that you must manually open up the divs to get to your specific element.

• It makes the working time more than 10 times longer to accomplish tasks that were once possible before.

I'm hoping this is just a setting that was reset by accident at my fault.

I also noticed the inspector theme switched to dark, if that helps.

Thank you

Hi everyone, I'm having trouble using the inspector tool for Firefox 54. • The problem is it no longer pinpoints elements as it once did previously. • This requires you to select an element but it will only select the parent element, to find a specfic element within that you must manually open up the divs to get to your specific element. • It makes the working time more than 10 times longer to accomplish tasks that were once possible before. I'm hoping this is just a setting that was reset by accident at my fault. I also noticed the inspector theme switched to dark, if that helps. Thank you

All Replies (6)

Is this of any use : https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector

Please let us know if this solved your issue or if need further assistance.

Hi Pkshadow, thank you so much for your help.

I did review this but unfortunately I'm still having an issue with inspecting elements.

Watch the first video here: https://developer.mozilla.org/en-US/docs/Tools/Page_Inspector/How_to/Examine_and_edit_the_box_model

Notice the elements being highlighted as the inspector hovers over them.

Here's what happens when I inspect the same page: https://streamable.com/s/w2k7r/wybqry

You'll see that mine inspector isn't even grabbing anything. And when it does, it only grabs the parent elements, in order to select an item I have to filter through the divs to isolate the item.

Am I missing a setting that I have overlooked?

Thank you

You can try to disable hardware acceleration in Firefox.

  • Options/Preferences -> Advanced -> General -> Browsing: "Use hardware acceleration when available"

You need to close and restart Firefox after toggling this setting.

You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.

Hi cor-el,

Thank you for your help.

Yes, hardware acceleration is enabled and graphics drivers are up to date.

And my computer has pretty good specs:

- Dell XPS 15 9550 / Intel i7-6700 HQ/ 16GB Ram - 60Mbps download / 10Mbps upload - Windows 10 - Firefox 54.0

Even since Firefox 54 came out I've been having major problems with the inspector, pages not loading (when opening in new tabs) and Gmail not sending email.

All of this never happened in previous versions of Firefox.

Does it make a difference if you disable hardware acceleration?

No difference, honestly my computer is pretty fast so I'm not sure what's causing this.

I just installed Chrome and tested the inspector, it was lightning fast compared to Firefox, I also had the same plug-ins installed.

ABP, Ghostery, uOrigin.

Chrome also performed without any lag using the inspector in responsive mode on some sites that crawled to load when using Firefox.

I have loved and used Firefox as my sole browser for the last 10 years but I fear with the persisting slow performance it's time to move on, and very unfortunately at that - I have grown to really enjoy Firefox over the years but again, the performance is just too slow that it's become stressful to use and it's taking away from my time and overall productivity.

I do appreciate your help and efforts cor-el, thank you again!