I tried debugging Firefox with Jetbrains Rider. But i got the error unrecognizedPacketType, Actor server1.conn1.tabDescriptor1 does not recognize the packet type 'attach' .
Followed link: https://www.jetbrains.com/help/webstorm/debugging-javascript-in-firefox.html#ws_js_debugging_in_FF_debugging_session
Versions:
Rider(2020.1.3)
Firefox Developer Edition(79.0b3)
Is there still a bug of Firefox, or Rider is not fully supported? Please help me!
Thank in advance!
UPDATE 7/2020
I asked on the JetBrains site. They said that due to changes in FireFox API. Debugging in Firefox now is not supported. They will fix it soon!.
I've found that using a JavaScript Debug configuration works but if I really need it I just use the Debug tab in the Firefox dev tools
I am using Firefox 50.0. After auto update of Firefox to version 50.0, Firebug has stopped working and attempting to use it is showing an inbuilt Firefox console while inspecting any DOM element.
Is there any patch to use Firebug on Firefox 50.0 version?
Solve The problem by Changing Mozilla Browser Configuration Settings.
Open A Blank Tab
type about:config in address bar then press enter (click on I accept the risk!)
find browser.tabs.remote.autostart
select the option then click the mouse right side
Turn The Option As False
Close the browser for restart browser
open browser again, inspect the element. I hope It Works Properly.
I manage to get Firebug work again, so here is what I done.
Everyone knows that Firebug isn't being developed or maintained any longer because it can't work with e10s, so here is my workaround:
Download Firefox Developer edition so you can allow XPI installation.
firefox-53.0a2.en-US.win64.installer.exe or
firefox-53.0a2.en-US.win32.installer.exe
Run Firefox developer edition after installing and go to the about:config (type in url bar)
Find xpinstall.signatures.required (set to false)
Find browser.tabs.remote.autostart (set all to false: browser.tabs.remote.autostart.1 and browser.tabs.remote.autostart.2)
NOTE: The Multi-process architecture improves the browser's stability, performance and security by separating tasks into processes, you disabling it at own responsibility.
After that you need to restart the browser.
Now you can go at the Firebug repository and install desired version
Here you can find all Firebug installations
I chose latest firebug-2.0b8.xpi and it forking fine.
P.S. You can disable updates for Firefox Developer edition.
Hope it helps.
Head over to Firebug website, you can see following message:
The Firebug extension isn't being developed or maintained any longer. We invite you to use the Firefox built-in DevTools instead.
Also Sebastianz told me,
Firebug is discontinued. The team has split up, the former team leader Jan "Honza" Odvarko is working on the Firefox DevTools now.
As #Makyen said in his answer, Firebug does not work with multiprocess Firefox, so remove Firebug right now and try Firefox DevTools instead, it's not optional (sadly), unless you don't update Firefox :)
Update 1
Take a look # Why got Firebug removed after updating Firefox to version 50?
Update 2
Take a look # my answer here: how to revert firebug to old version
Firebug does not work with multiprocess Firefox
The Firebug site claims that:
Firebug 2.0.18 is compatible with Firefox 30 – 52
However, it also explains that [emphasis mine]:
Firebug 2.0.18 fixes issue 8030. The extension is marked as multi-process (e10s) compatible so, it isn’t blacklisted and users can continue installing it. This way Firebug can help users to easily migrate into built-in Firefox developer tools – in case it’s running in multi-process enabled browser. When opened in a multi-process Firefox, Firebug’s tools cannot be used. Firebug will then only assist the user with migration to Firefox’s built-in tools.
They also direct you to read: Unifying Firebug & Firefox DevTools
That page says that [emphasis mine]:
Firebug 2 doesn’t work in multi-process browsers (i.e. e10s) and converting it is too complex, so it will stop working when e10s is activated in Firefox. You will be able to disable e10s for a while to keep using Firebug 2, but this won’t last forever.
The fact that Firebug does not actually work in multiprocess Firefox will account for different people having different experiences with Firebug working or not working in a particular version of Firefox. Firefox automatically enabling multiprocess mode will depend on multiple factors, including what other add-ons are installed in the profile.
Using Firebug in newer versions of Firefox
Thus, to use Firebug in newer versions of Firefox, you will need to disable Firefox from entering multiprocess mode. This can be done from the about:preferences page (also available from Tools➞Options). This an option which is under the "General" tab as "Enable multi-process Firefox ...". If multiprocess is not available, this option will not be shown. This option can also be changed by adjusting the preference browser.tabs.remote.autostart from about:config. [Note: browser.tabs.remote.autostart.2 and browser.tabs.remote.autostart.1 also appear to be used to indicate default states, thus I suggest using the about:preferences page to change this option.]
You can determine if your Firefox is currently running in multiprocess mode by looking in about:support. The line "Multiprocess Windows" under "Application Basics" will state if multiprocess is enabled or disabled.
Set up profiles explicitly for testing
Personally, I have different profiles set up for each of multiprocess explicitly disabled and multiprocess explicitly enabled (set browser.tabs.remote.force-enable to true), so I can perform testing under both conditions, with the state of multiprocess being enabled/disabled being known in advance.
I had the same problem when I updated Firefox. I was so addicted to firebug but I moved on to Firefox developer edition - https://www.mozilla.org/en-US/firefox/developer/
It also comes with the firebug theme which resembles firebug UI and its efficient.Just install FDE and activate the firebug theme as shown in the image below :
I had the same unexpected surprise when ubuntu updated FFX and suddenly things like the script panel stopped working. Since I was in the middle of working on something with a short deadline, I was not going to have the luxury of learning the firefox developer toolset and desperately needed to get firebug working. The fix that finally worked for me was to set Firefox preferences not to update. Then download v 49.0.2
https://support.mozilla.org/en-US/kb/install-older-version-of-firefox
I also had to tell Ubuntu not to include firefox in it's upgrades.
It looks like firebug will no longer be maintained as a seperate project, so you will want to get familiar w/ the built in dev tools, but hopefully this buys you some time. Worth mentioning (if I'm reading this right, it sounds like it will be integrated into the native tools:
https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/
https://github.com/firebug/firebug.next
Its working. You need to install one more add-on "Firepicker" and restart the Firefox.
https://addons.mozilla.org/en-US/firefox/addon/firepicker/
I managed to resolve this issue by simply downgrading to mozilla old version using this url:
open https://ftp.mozilla.org/pub/firefox/releases/50.0/win64/en-US/
download and run the .exe setup
Go to Settings - > Add Ons
Click on extensions and search for firebug and firepath and then add those extensions
Hope this should resolve the issue. For those using Windows 32 machine can use the url
https://ftp.mozilla.org/pub/firefox/releases/50.0/win32/en-US/
http://toolsqa.com/selenium-webdriver/xpath-helper/
Open a new tab and navigate to any webpage. I have used www.DemoQA.com for demo.
Hit Ctrl-Shift-X (or Command-Shift-X on OS X), or click the XPath Helper button in the toolbar, to open the XPath Helper console.
Hold down Shift as you mouse over elements on the page. The query box will continuously update to show the XPath query for the element below the mouse pointer, and the results box will show the results for the current query.
If desired, edit the XPath query directly in the console. The results box will immediately reflect your changes.
Repeat step (2) to close the console.
After updating Firefox to version 50.0 my Firebug opens the default developer tools. The original Firebug doesn't work anymore.
I have always preferred Firebug as my default debugging tool. I want the original Firebug back in Firefox 50. How can I do that?
Firebug does not work anymore once multi-process Firefox (separate processes for the Firefox UI and the websites) is enabled. See the related post in the Firebug blog.
You may be able to reenable Firebug by setting the preferences browser.tabs.remote.autostart, browser.tabs.remote.autostart.1 and browser.tabs.remote.autostart.2 to false via about:config. Though at some point this preference will be removed.
So, you are advised to use the Firefox DevTools instead. I am writing a migration guide on MDN. Firebug features that are not in the DevTools are covered in a Firefox bug.
First remove new version of "firebug" and download old version of "Firebug(2.0.17)" from following URL:
https://addons.mozilla.org/en-US/firefox/addon/firebug/versions/
Uninstall Firefox completely including deleting the Mozilla folder within your APPDATA.
Then reinstall Firefox and add both Firebug and FireQuery.
After that everything should work as before.
You can also go on Help -> Troubleshooting Information -> Refresh Firefox and install Firebug through http://addons.mozilla.org/
For all the folks out there, there is a good news..!! Firebug works great on these two Mozilla based browsers.
Cyberfox & Palemoon
Both are forks of forefox that uses code before the implementation multi-process. Cyberfox uses the more recent code fork compared to Palemoon.
Both browsers are well maintained and updated regularly.
Cyberfox announced its death on March 2017 but its still actively maintained [as of Dec 2017] and I still get update.
Both browsers support cross platform windows / Linux, on Linux you should have 64 bit distro to use cyberfox. Palemoon on the other hand works great on both the bits.
Actually i have used the Firefox below release of 40. Firebug is not working properly cant able to debug the script. Is it possible to update the new version every time.
Firefox has a debugger now! Go to Tools > Web Developer > Debugger.
Here is the documentation and an instructional video:
https://developer.mozilla.org/en-US/docs/Tools/Debugger
I have a webapp which is tested by selenium. Everything works well: writing tests in java, setting breakpoints in my webapp through firebug.
unfortunately I am not able to debug the user-extensions.js it self: After starting the java-test, two firefox windows are opened. One holds the webapp to test, the other one holds the data-flow which uses the user-extensions.
How can I debug the user-extensions?
It seems that it is not possible. I made a workaround and switched the functions to my webapp to debug them there.
It really depends on the browser you're using. I've been able to debug user-extensions using Chrome. In the control Window, you need to right-click and then view the window as a tab. Once you do that, you can activate the developer tools for the control window, which will include the JavaScript debugger.
It's possibile using the Venkman debugger (a separate Firefox extension) and Firefox up until version 32, and that's quite a precious combination.
With Firefox 33 and later, Venkman is broken by api changes, and the native debugger unluckily doesn't allow to debug xul based extensions.