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.
Related
How can I completly deactivate firebug without uninstalling it?
I installed firebug because there are some cool extensions like "Firepath" so you can read out the Xpath. However, there are also some missing features which are included in the normal dev console, e.g. manipulating the CSS of the currently selected element.
So to use these features I have to switch back to the normal developer console. However, firebug is still active after deactivating the addon.
Still appears in the menu at the top:
And if I press F12 then Firebug opens.
Normally, deactivating an extension within the Add-on Manager, like you did, completely deactivates it.
When it's still activated, it's a bug and you should file a bug report.
Having said that, note that Firebug's development is discontinued and it will not work anymore once multi-process Firefox is enabled. Furthermore, Mozilla plans to stop supporting extensions that are not based on the WebExtension framework starting from Firefox 57, which is released in November 2017. At latest at that point in time Firebug (as well as most existing Firefox extensions) definitely stops working.
Regarding the XPath features, there are several feature requests filed for the DevTools already asking to implement advanced XPath support.
Fellows I am having a huge trouble with an project in Ionic and I want to use a dedugger in order to solve more effficiently.
Do you know how to use a debuggger in order to achieve that;
If the answer is the firefox debugger how I will use it in order to debug my application?
For Mozilla Firefox, the following are different ways to set a breakpoint within the JavaScript code in the debugger.
For Google Chrome, since this is the JavaScript you can also use Debugging with breakpoints (Debugging JavaScript). This will help you a lot.
More about debugging: How to Properly Debug Your Ionic Application.
I have a problem that causes Firefox to behave strangely during startup.
(Specifically, it displays the "Firefox seems slow... to... start" message, even though I didn't install any new extensions or anything like that.)
The function that displays that message is _showSlowStartupNotification in browser/components/nsBrowserGlue.js which is called from _trackSlowStartup which in turn is called by _onFirstWindowLoaded.
I want to debug that. How can I do that?
I can debug the Firefox binaries easily with WinDbg and Mozilla's symbol server. But that's not what I want. I want to debug the XUL, not the C++.
I can debug the XUL if I enable the Browser Toolbox, but only after the startup. Even if I set devtools.debugger.prompt-connection to false and run firefox.exe -jsdebugger to immediately open the Browser Toolbox, I get access to it only after the startup code has already been executed. Setting a breakpoint on the interesting function doesn't help as they are not persistent; restarting Firefox doesn't cause the internal XUL debugger to break on them.
So, any suggestions? Is there a way to debug Firefox's XUL from the early start?
Are there any tools/methods for debugging phonegap Blackberry(5,6,7) app . Presently am using Alert for debugging which is very tedious .
Since you are using PhoneGap, its always better to view/debug you app on a webkit browser like Chrome/Safari. Also try Ripple emulator from BlackBerry which is the best web emulator for mobile devices: https://chrome.google.com/webstore/detail/ripple-emulator-beta/geelfhphabnejjhdalkjhgipohgpdnoc?hl=en
Since you are developing a web app, and as far as I know there's no "official" IDE for BlackBerry Webworks, this question is not BB or Phonegap specific. You are just asking how to debug JavaScript. There are a lot of questions in SO about this, just run a search. I'll give you my two cents:
As the JavaScript code runs in a browser, you need to debug in the browser. Most browsers have built-in debugger or extensions. For Firefox I'd reccomend Firebug extension, in Chrome the built-in debugger is pretty good. I can't tell about IE but I think there's something similar.
If you need to debug on device, then use console instead of alert.
Finally, have a look at WebStorm. Probably the best IDE for JavaScript right now, but you need to purchase a license. It allows you to attach to the browser debugger and debug in the IDE.
Looking forward to the TideSDK 1.3 release. I've extended the sample app provided but I'm unable to figure out how to breakpoint my code and step through it for debugging purposes. Of course when running in the browser I can use chrome debugging tools but in the Tide sandbox how do I accomplish this?
One way to achieve this is to open up the inspector inside the app and use the webkit inspector to breakpoint and step through your source code.