I'd like to open up a new chrome window (not tab) and have it take focus in its address bar immediately.
It works when pressing CTRL+N to open the new window (presumably from the current process) but not when clicking the Icon in the quick launch bar or on the desktop (thus launching a new process).
Then it just opens up, comes to the front, cursor blinking in the adress bar, but it does not have focus there. Typing sends the input to desktop I believe since no open program seems to have the focus then. This is particularly annoying when I was working with a different program and want to have a new browser window.
My Chrome version is 23.0.1271.97 on Windows 7 x64, and as far as I remember it worked fine until version 17.
I just published a small Chrome Extension which aims at solving this bug! So far it worked great for me (on Window 7 64-bit).
You can find it here: https://chrome.google.com/webstore/detail/chrome-new-window-focus/opmhcfhkhiodgapmnaolhmekmfihmecp
Let me know if you encounter any issues!
Cheers,
Yuvi
Related
I have been fatal for a few days with this incident. After the latest Chrome updates I am left with a headache.
We have ASUS v161 touch screens (although it happens to us in more models), and we open the chrome in kiosk mode. The power configuration is high performance and we only turn off the screen after 15 minutes (no sleep). We have also tried disabling anything that turns off the hard drive or usb without success.
We have tried to activate all the touch flags, we have deactivated the hardware acceleration, etc ... But it is happening with the last 3 updates.
Chrome version: 88.0.4324.150 (Official Build) (64 bits)
Windows version:
Windows 10 Pro Edition
Version 20H2
Installed on 09/25/2020
Operating system version 19042.746
Windows Experience Feature Experience Pack 120.2212.551.0
The issue is that when you return from the off screen, by touching with your finger, the screen turns on but the web content that chrome shows does not respond.
If we do not open it in kiosk mode, it does not respond until we touch anywhere in Windows or in the chrome address bar, then it begins to respond. But the web does not respond by itself if we do not touch outside of it. The web is frozen, te text cursor are freeze. (This also happens with Edge) It does not happen with Firefox.
If you hit it with the mouse, no problem, all return to be responsive
Video attachment: https://youtu.be/BH2abO6AXaM
In the video it is clear how the system activates the screen with touch, but chrome is frozen, the cursor does not move, it does not respond to any link, there is a moment where the screen goes blank, and at the end you see how it responds when I touchthe address bar. This happens right away if you hit the address bar or any other windows/desktop of Windows.
When Chome wake up all touch response are ok and the cursor blink again. If like's Chrome still sleeping until other event different than touch success.
Thanks a lot
Jorge
I was having this problem too for a few months, but it went away with Chrome v91. Upgrade to the latest version of Chrome if you're still on a lower version.
Until recently when I have the dev-tools open in Chrome, a little window-size display would appear in the top-corner of the window. This has now stopped appearing. Has anyone else experienced this or know how to get it back?
I have a feeling that Chrome may have updated recently as I know notice a .cls button in the styles tab when using the element inspector. Am now on Version 49.0.2623.87 m (I have seen there was an update on the 8th March)
Thanks
When I bring up the dev tools in Chrome Canary, it just appears as a black box. I have it set to display in another window rather than overlaying the actual page, but as said, the inside of this window is just black. If I hover the mouse over it, it highlights the elements on the page accordingly.
I have tried: Looking for settings to dock it back into the screen, restarting CC, restarting my computer, reverting to default settings in the CC menu. None of this has changed a thing unfortunately.
EDIT: Has been resolved with update to version 33.0.1707.0
Same thing happened to me, starting sometime in the past two days. I tried everything you did and also tried reinstalling Chrome Canary, no dice. My solution was to dock the developer tools back to the main browser window by clicking in the upper-right corner of the black box, where I think the dock icon usually is.
I'm running Ubuntu (12.04.1 LTS) using VirtualBox (4.1.14) on a Windows 7 host machine. It seems that, using Chrome (21.0.1180.89), CSS transformations are causing the browser to lock up in a strange fashion.
This can be tested using this page: http://benmurden.com/css3test/css3test.html
In short, it looks like the "content area" of the browser, that is, anything apart from the URL bar, tab list etc. stops rendering during or after a CSS transformation and becomes "stuck" on top of every other open process. I can still close the offending tab or the browser itself since that area of the browser is fully responsive. I can even switch to another process and it will be partially visible under the "stuck" content area on top of it.
I meant to take a screen cap to demonstrate this particular effect but after locking up Chrome in this way and switching to a text editor behind it, only the text editor was fully visible on the screen cap and the locked-up Chrome was nowhere to be seen. This leads me to believe this might be a problem with VirtualBox rather than Chrome itself. Then again, there is someone sitting next to me with a nearly identical setup: Same type of machine running Chrome on Ubuntu using VirtualBox with identical versions of those three and he does not experience this issue.
I am unable to reproduce this on any other browser and host/guest combination I'm currently using. Those are:
Firefox (15.0.1) on Ubuntu
Firefox (15.0.1) on Windows 7
Chrome (21.0.1180.89) on Windows 7
Please let me know if there's any other information I could supply that would be of use.
Thanks!
I'm building out my jquery mobile app out and have been testing in Chrome. Its the best for me because the debugging is great.
I was using a TAPHOLD event but decided to go away from that for a swipe-right event.
Chrome actually registered the taphold, so I was hopeful that it would register a swipe right with the mouse. But I cannot get it to register unless I have to do something else... anyone?
By now the actual chrome developer tools (tried chrome 20) can emulate touch and swipe events.
You can activate that behavior through the tool options, accessible via the little gear-wheel in the bottom corner.
Just check "Emulate touch events" from the options. Then you can also swipe with your mouse.
In desktop browsers I tend to use the right mouse button testing swipes. It will open a context-menu but it actually works (I normally use Chrome 17 and Firefox 10).
For instance when left-clicking and then swiping on an image in Chrome or Firefox it selects the image and you are then moving around the transparent thumbnail of the image. But when right-clicking and swiping the swipe event is fired.
UPDATE
This update is pretty late to the punch but this just shouldn't be necessary anymore. In fact the Chrome developer tools (the ones I'm used to using) have gotten a lot better about emulating devices.
A lot of the answers here are old and out of date. As of Chrome 63, swipe is built-in as long as you are in responsive mode with developer tools open. So open Developer Tools (3 dots->tools->developer tools), then click the phone/tablet icon on the left to put Chrome into a mobile mode. Then if you left click and hold, you will see the cursor changed to a dot, and you can swipe.
Update: this appears to be enabled in Chrome by default (37.0.2062.120 as of September 2014) you do the following:
Open Developer Tools
Click the little phone icon next to the search icon in the upper left (next to the Elements tab)
In the Emulation tab on the bottom choose a device model from the drop down
Previous answer:
To get this working in the current version of Chrome (32.0.1700.107 as of Feb 2014) you do the following:
Open Developer Tools
Click the gear icon in the upper right
Select the Overrides tab on the left
Click on Show 'Emulation' view in console drawer
Close the Settings popup
Open the Console (button to the left of the gear)
Click the Emulation tab in the console (next to Console and Search)
Choose a device and click on Emulate (and click Reset to cancel emulation)