Google chrome freezes when printing a page using window print method - javascript

I have latest google chrome version -32.0.1700.107 m installed on windows 8 machine.
I am doing this:
popup = window.open();
popup.print();
This opens a new popup and a print window appears. Now, when I go back to the page from where I triggered this, it freezes and I cannot do anything there.
Here is the small fiddle for your reference. FIDDLE
Click the button and come back to the fiddle page (do not close the print page) and try typing anything in the fiddle, it will be hanged and as soon as you will close the print page, the fiddle window will get normal.
This is in Google chrome ONLY, other browsers are working smoothly. Please help.
I tried:
Opening the popup in new window using window.open("","","width=800,height=600").
Putting popup.close().
opening it on some different OS (windows 7, XP)
But got no success
Please some kind soul help me with this issue or some work around.

This is an issue in Google Chrome and will be fixed in Chrome 36 according to this issue.

Related

Developer Tools in Google Chrome not showing

I'm just moved to windows 10.
And have latest version of Google Chrome on it.
But whenever I tried to access developer’s tool it shows nothing.
I have tried,
1) Right Click + Inspect element.
2) F12.
3) Right corner tab on Google chrome + more tools + developers tool.
But none of them working.
Please help.....
I don't know what is missing.
I had the same issue but in my scenario I was on a Virtual Machine with some complex display settings. The procedure here worked for me in other contexts:
You should see the process in the Windows bar on the bottom of your screen.
When you click on it, nothing is shown.
Bring back in the viewport
If the conditions above apply, then the window is simply displayed out of the display viewport. TO bring it back, do the following:
Make sure you have selected the window in the Windows bar.
Hit ALT + SPACE to show the menu
Select "Maximize".
The window should appear in one of your monitors.
Drag it around and resize it.
You should try also Ctrl+Shift+I for windows as written on the following doc
https://developers.google.com/web/tools/chrome-devtools/
I fixed this of this way
Open chrome dev tools
using the chrome page that you need debug press Win + "<" (left arrow)
windows ask you which window you want to the right and select chrome dev tool icon, but click should be in the icon instead of the rectangle of the windows
Just had the same problem. The window is apparently minimized.
On windows, hold the mouse on the chrome icon in the taskbar, when the thumb shows up, right click on it and select maximize window.
First thing i would try is closing all processes and restarting Chrome and if that doesn't work i would uninstall and reinstall chrome
I know this isn't really an answer but hope it might help
Goodluck!
Chrome -> Setting -> Extensions (Side Menu) -> Turn on Developer Mode
Had the same issue, The thing is just minimized. Hover over the side of the options at the bottom and drag to top and you will see the options.
see following image and hover over ht area highlighted in yellow
Your dev-tool might be on your second monitor, which you are not looking at but connect with your PC.
Disclaimer: Please try this at your own risk, I'm not fully aware of its consequences. It apparently clears chrome's local storage for all websites
All the solutions I saw didn't work for me, but this one did:
I deleted this folder:
// AppData\Local\Google\Chrome\User Data\Default\Local Storage\leveldb

Open about:blank window in firefox

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()

Chrome & PopUp window names

I am opening pop up windows from a website (flash content) the following way:
RING = window.open(path,'RING_Projekt','width=800,height=600,scrollbars=no,top=' + t + ',left=' + l +'');
The HTML file opened in the popup is valid HTML with a <title>, yet Chrome (all other browsers do work fine) will display "Untitled" in the title bar.
Does anyone know why this is happening and if there is an error / workaround that could fix this? Or is this some kind of a pop up blocker malfunction / bug?
Thanks!
EDIT: Playing around, I noticed the following (unfortunately it ADDS to my confusion...): the page with the flash content opens another popup (displaying news) on load by doing:
var NEWS = window.open('popup/news.htm','RING_news','width=400,height=400,scrollbars=no,top=20, left=20');
When I now open a popup with the function mentioned in the above post, then go and close the news-Popup opened on load and then switch back to the "on-click"-Popup the popup magically acquired a name. When you close this and open it again, the name is gone again.
To be honest: I don't get it. I should be able to have more than one pop-up, right? Also, I cannot see any naming problems or anything else that could explain this behavior.
Am I missing something big here? Or is this a plain bug?
Ok, I am a 99.99% sure this is a Chrome bug, so I'll answer this myself.
Chrome seems to read the specified title correctly from the HTML (as it will be displayed in the task bar), but seems to have problems when having to display the name in the bar on the popup (see screenshot below). When you start to fiddle with the popup (move / resize), the title will sometimes appear and disappear again. Yet, the names in the task bar will always be right (that plus the fact that it works in every other browser lets me think it is a bug).
I am running Chrome 14.0.835.186 m on Windows Vista.
http://code.google.com/p/chromium/issues/detail?id=113201
its a open bug
This is a bug with Chrome. However, there is a workaround for this.
If you put the following script in the page that opens in the popup window, it seems to work fine.
<script language"text/javascript">this.window.resizeBy(1,1);this.window.resizeBy(-1,-1);</script>
The second argument to window.open isn't the <title> of the new window, used by <a target="...">, for example.. The title is determined by the content of the page.
See MDN docs for more info.

Colorbox not working in IE

on This page in the center is a button that says "request price". I am using Colorbox so that when you click it, there is a lightbox-type popup of a Flash app.
This works fine in FF and Chrome. However in IE it is just taking you directly to the page containing the flash rather then making it a popup.
Does anyone have a clue why?
I am not sure whats wrong with your code but if you can try this:
jQuery('.verragio-shanks').click(function(){
jQuery.fn.colorbox({href:"http://www.google.com"});
jQuery.preventDefault();
});
replace google.com with your link

Strange behaviour opening pop-up window in Internet Explorer

I have the following JavaScript code to pop up a window in Internet Explorer. The code is executed from a page within a Microsoft CRM modal dialog box. (RequestID is a string that is always the same in the test system - at the moment it contains "abcdefg" - without the quotes).
var cancelUrl = "CancelRequest.aspx?RequestID=" + RequestID;
alert("About to open a window.\n\n" + cancelUrl);
window.open(cancelUrl);
alert("Window opened");
I expect to see a message telling me that I am about to open a window. I then expect to see a window open and get another message about the window having been opened. I don't really care about the order of the last two events; the alerts are there so I know the code has been executed.
I have two PCs and a virtual PC. All running IE7. On the Windows 2003 VPC, the messages and pop-up appear every time without fail.
On the Vista PC and WinXP PC, the messages appear but the pop-up only appears intermittently. (I think this may be the case on the Vista PC too).
All three have identical settings in IE. All have the IE pop-up blocker disabled and have no other pop-up blockers installed.
Can anyone shed any light on this?
Ah, I think I got it... missed it in the description...
You are trying to open a non-modal window from a modal dialog in IE.
This AFAIK, should not work.
Try opening another modal window instead.
Effectively you are saying...
on window A, open up modal window B, now open up non-modal window C, which isn't really valid.
This code is simple. Use debugger and see what is going on.
Check that site with FireFox or Chrome, they have JS debuggers.
Edit:
Add try/catch block around window.open() and see if there is some exception there.
Edit 2:
I see now that you are sending characters as RequestId. You should check if that URL can handle that kind of value. Since name is RequestId I'd say that there is big chance that there should be numeric only parameter. If that is correct, then it can happen that server side crashes when you try to open window and then nothing happens. Reason more to set try/catch block and test.
You might want to try Firebug lite, which will work for IE.
http://getfirebug.com/lite.html
The try/catch other people have mentioned is also a good idea. I think.
Additionally, is there any chance that the pop-up is trying to use a window that is already open but minimized. So it doesn't appear to be working but it's really just reloading the minimized window?

Categories

Resources