I'm trying to debug an iframe's contentWindow, but every time i try to view the contentWindow object on chrome 59 dev-tools the page crashes.
It happens when hovering the contentWindow property on breakpoint or when clicking on the console logged object.
I'm using ReactJS so i created a react fiddle although i don't think that's relevant.
Fiddle to reproduce:
Open the dev-tools
Click "Try-it"
Click the console.logged object.
Is there a way to avoid the crash?
This seems to be fixed on chrome 60 thanks to the new context selection. feature
Related
Basically, I need to open a window. I need to fill this window with HTML. Now here is my issue. When I do something akin to window.open().document.write("HTML"), it doesn't show up. It simply shows about:blank and a blank white screen as if I never wrote to it. I've already tried using the window's document.body.innerHTML to write to it, but I recieve the same results. I've been able to recreate this in my script and in Chrome DevTools, so it's not an issue with my script.
It turns out that for some reason, when running this on the Chrome New Tab page(it's a chrome extension that needs to be able to run outside of a chrome extension), it doesn't work. I don't know why this happens, but it does.
When debugger is enabled in firefox by pressing F12 it is disabling the editing feature in the website for which debugger is opened for. Firefox version is 58.0.1
The new UI of firefox is having some problems for me. Once I open the debugger UI cannot do any operations on the web page. Hence went back to old UI by setting the below property to false in browser.
Go to firefox browser. In the address bar type, "about:config". Without the quotes. Search for the below property and toggle it. The value can be toggled(changed) by right clicking or by just clicking on the entry. Set this property to false which takes back to old UI.
property to be altered ==> devtools.debugger.new-debugger-frontend
One of the easiest ways to fix any error is to reset your Firefox under about:support. Lookut for somethin like clean or refresh or reset
When i open a new window using window.open javascript, chrome opens with about:blank, but firefox opens with jsfiddle back url and if you right click on the page, you can still see the page loading. You will not see the refresh icon, instead a stop icon is appearing.
I need to open the new window with about:blank.
Here is the jsFIDDLE
Tested with Chrome 45.0
Tested with Firefox 41.1
<button id="helper">Click here for help</button>
What you are experiencing is a new Firefox behavior that passed in version 40 or 41 (sorry I did not find the reference).
Expect it to become part of google's behavior soon too, you can see people requesting it already(Chrome issue)
Unfortunately there is not much that can be done for now as it is brand new people have not found workaround or even if it is a good idea to fight against the browser... My suggestion is to not use about:blank at all and use a blank html page from your domain, that would make things easier on the users.
Instead of about:blank take #:
$("#helper").click(function(){
windowURL = window.open("#","Looking ....
EDIT
in order to prevent the browser from showing an "infinite loading", close the document:
...
openedDocument.open();
openedDocument.write(myHTML)
openedDocument.close()
I am trying to understand WTF is going with Internet Explore 9, this no mean feat in itself.
I thought the problem was due to browser comparability issues but now I am unsure.
On the staging server I have set the header to Header set X-UA-Compatible: IE=Edge, but it is having no effect.
For example, If I reset the browser, and then open the URL:
http://www.45sound.com/shows/259-heathers-trinity-college-dublin-18-9-2012
Clicking on the timeline, does not move the nob or change the video.
HOWEVER, If I open developer tools, clicking F12, then close it, without reloading the page, it works perfectly...
Is this a loading issue, does anyone know what is going on? I am unsure why this action has an effect on the javascript.
Any help at all would be really great.
Sounds like your code has problems with the weird implementation of the console object in IE - it does create the object only if the devtools are open. See also
Does IE9 support console.log, and is it a real function?
What happened to console.log in IE8?
'console' is undefined error for Internet Explorer
What the Head Said: Internet Explorer 9′s problematic console object
Got this page which has some javascript on it (very heavy) and I am trying to see what happens when I click a certain element. However looking at the code there is no onclick function - the javascript is several JS files so take far to long to browse.
Is there a way with Firefox (firebug), Chrome or even IE to view whats / log what is happening when I click on an element in the browser?
In firefox (and this is also available in chrome and IE in another form) install addon firebug (if not installed). Go to Tools->Birebug->Open Firebug. Click on Left Icon and ask for tracing.
You can then trace your program.
Another way is to cause a breakpoint when you start, and you manually follow the execution of the script.
Chrome Developer Tools shows all attached event handlers for an element. See the section on Event Listeners towards the end.
#wizzard, try this: firebug - profiling button
ff only, but there is a lite version for chrome for example