Console in lower pane that catch syntax errors - xul

While creating an extension in Firefox, I'd like to have real web console at the bottom of the screen.
I tried Firebug's console but it doesn't catch syntax errors, and the other ones I tried do not catch these either.
I also tried to put the webconsole.xul into an iframe into my own xul file. The console appears, but it is not working.
<iframe src="chrome://browser/content/devtools/webconsole.xul" flex="1"/>
I guess this could have been expected. Is there a way to have a console in the lower pane that catch JavaScript syntax errors, as the Browser Console does ?

I took the erroneous assumption that Firebug can't catch syntax errors, since I couldn't catch them myself with the "onerror" event handler.
I just had to check "Show Chrome Errors" in the console options of Firebug.

Related

Breakpoints in Safari dev tools get enabled automatically

Each time I load a page with Safari dev tools opened (no matter which tab), some breakpoints get triggered and I get redirected to the Sources tab with the message "Debugger Paused".
The problem is that I didn't set any breakpoints, at least, intentionally, and these redirects don't let me review the source code or load webpages properly.
Even if I disable them, they get re-enabled as soon as I reload the page. I'm failing to understand why this happens.
I see two breakpoints in the Sources tab: All Exceptions and Uncaught Exceptions, but they don't seem to be enabled.
Unfortunately, I couldn't find how to disable the debugger or locate those exceptions. There are no options to do that in the context menu if I right-click the "Debugger Paused" message, disabled exceptions in the Sources tab or Safari settings.
Has anybody come across similar issues or know how to fix that behavior? Any help is much appreciated. Thanks!
Safari 13.1
macOS 10.15.4
Here's how it looks like
You click "+" next to the Breakpoints, then you click All Requests. And then it will appear in the list and is enabled by default. You click disable - VIOLA! See the attached image.

Selenium webdriver "Error communicating with remote browser. It may have died" when I run test in parralel

I am working on client side. I have created around 150 test scripts. But during execution, after some script execution, Selenium throws below error and it close the browser. Time is not a fix for this error. It comes when I am executing all the test scripts together in parallel.
The error shows on Google Chrome and Firefox browsers. I am using selenium-server-standalone-2.26.0.jar file and doing execution on FF 13.0.1 version. I have also tried with FF version 14, but I get the same error. My client is not happy with this error because we dont have workaround for this issue.
**Error message:**
Caused by: org.openqa.selenium.remote.ErrorHandler$UnknownServerException: Error communicating with the remote browser. It may have died
I think this will happen when you dealing with popup window.
Example
Working on main window clicking on something leads to open a new popup
switch the control to popup window & do your operations in pop-up
Most of the cases popup will be closed automatically after some action performed in it. (EX : Login with facebook option most of site now a days, after entering user credential no need to close that popup it will be closed automatically after submitting proper credentials)
After this you need to switch the control to main window again otherwise it will throws above exception.
I think your doing some operations without having the control over a window.

handling showModalDialog window in selenium

I am using Selenium- JAVA to automate my application. In my application, when we click on a particular button, it actually opening a window using showModalDialog command. When we open a window using showModalDialog the java-script execution gets suspended till the window gets closed.
Problem No :1
in Internet Explorer(7,8,9), i am getting permission denied error upon clicking. I also tried executing javascript. For this also i got permission denied error. Any idea about this issue?
Problem No:2
In Firefox, i executed the same script and it is working fine. But the problem here is execution is suspended and it will not execute the other commands till the model window gets closed.:( How to solve this issue?
You will have to do modifications in selenium browser bot js-IEBrowserBot.prototype.modifyWindowToRecordPopUpDialogs to handle the modal window-this will help Try this. Or try using webdriver.
Can you post the application HTML you are getting this error on?

Does ExceptionHub break Selenium's wait_for_page_to_load command

I just added ExceptionHub (a javascript error tracking service) to our website, but all my selenium tests are failing now. When I look at the selenium output, it says it timed out in waitForPageToLoad command. If I run the test locally, I see that the page loads up fine, so I'm not really sure why selenium keeps waiting. Has anyone else managed to get ExceptionHub working with selenium?
I've seen similar problems with UserVoice. Often the rest of the page is loaded but still waiting for UserVoice and the test will time out.
It might help if you don't start loading ExceptionHub until the rest of the page is loaded. Of course that would mean you can't catch any javascript errors during page load...

script error in web browser

i have made a web browser in vb.net.but for few pages i find a msgbox displaying script error.
script error
! an error has occured in the script on this page
line: 86
char: 3
error: object expected
code: 0
url: http://songs.pk/
do you want to continue running scripts on this page?
yes no
or u can see the screen shot here http://dharmatejanaishadham.blogspot.com/
but still i'm able to open that page.is there a way by which i can avoid this script error.
songs.pk website has a number of unsafe JavaScript executions. All of these are from the ads you have placed on your site. These ads scripts are calling methods on your domain. This is a cross-domain request and unsafe. Get yourself FireFox and and install the FireBug extension on it. You will then see each of the error in detail and the source of it.
The error message is shown to you by the browser to avoid freezing itself by continue to execute these script. It is a good thing to catch bad script executions.