Unwanted update disables Firebug; I can't do without! I Have to use Chrome now, is that what you want?
I am webdesigner and Firebug and Firefox were always my friends. But all of a sudden Firebug doesn't work anymore, due to an unexpected update of Firefox! I don't want that! And now I have to use Chrome! Unbelievable!
Gekose oplossing
mvloon said
How was my English for a Dutch person?
Your English is great, but unless I interview many Dutch people, I can't answer your question precisely.
To clarify my previous comment, the "Inspect Element (Q)" item on the right-click context menu should open Firefox's built-in Page Inspector tool.
https://developer.mozilla.org/docs/Tools/Page_Inspector
If the site is blocking the context menu, you can change a setting in Firefox so that you (nearly) ALWAYS get the built-in context menu:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.
(2) In the search box above the list, type or paste contex and pause while the list is filtered
(3) Double-click the dom.event.contextmenu.enabled preference to switch the value from true to false
You will notice on some sites that the Firefox context menu now blocks the site's custom menu. On Windows, you can tap the Alt key to dismiss Firefox's context menu without dismissing the site's context menu. (If you press Esc, most likely both menus will be removed.)
Lees dié antwoord in konteks 👍 0All Replies (9)
Maybe this will help :
https://developer.mozilla.org/en-US/docs/Tools/Migrating_from_Firebug
Next time a _blank link is better; then I stay at the forum page. I have discovered this developer tool; but it doesn't work fine, not as fine as Firebug. It doesn't react on right mouse click, so to directly check that item!
Firebug has been quietly fading away for a long time. Here's the last substantive blog post I found:
https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/
mvloon said
Next time a _blank link is better; then I stay at the forum page.
If you figure out a way to do that in a forum post, let me know.
I have discovered this developer tool; but it doesn't work fine, not as fine as Firebug. It doesn't react on right mouse click, so to directly check that item!
Where are you right-clicking? Usually for HTML elements in a page you would get an "Inspect Element" item on the context menu.
Hi, I normally get a possibility to choose Firebug, but because nothing happened I began searching for the reason and discovered that Firebug had disappeared. It may be so that the website did not let me use the right mouse button, and that was the reason of not being able to inspect. But I thought it was the lack of Firebug.
How was my English for a Dutch person?
Gewysig op deur mvloon
Gekose oplossing
mvloon said
How was my English for a Dutch person?
Your English is great, but unless I interview many Dutch people, I can't answer your question precisely.
To clarify my previous comment, the "Inspect Element (Q)" item on the right-click context menu should open Firefox's built-in Page Inspector tool.
https://developer.mozilla.org/docs/Tools/Page_Inspector
If the site is blocking the context menu, you can change a setting in Firefox so that you (nearly) ALWAYS get the built-in context menu:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.
(2) In the search box above the list, type or paste contex and pause while the list is filtered
(3) Double-click the dom.event.contextmenu.enabled preference to switch the value from true to false
You will notice on some sites that the Firefox context menu now blocks the site's custom menu. On Windows, you can tap the Alt key to dismiss Firefox's context menu without dismissing the site's context menu. (If you press Esc, most likely both menus will be removed.)
Well, you are great, because the problem is SOLVED! I can now edit the CSS again! Thank you VERY MUCH!
Regards, Maarten van Loon The Netherlands
Maarten, would you be so kind as to mark jscher2000's post as 'Chosen Solution' ?
Bij voorbaat reuze bedankt ! (colloquial Dutch for 'Thank you in advance')
Oh boy ....... you inadvertently marked my post as 'Chosen Solution'.
But no worries, I'll get that rectified.