I've been developing a standalone Chrome App, and I noticed that I wasn't able to close the application window with ⌘+w. If I look in the menu, it shows up as just w, which doesn't actually close the window when pressed. Clicking it from the dropdown works as expected.
It does this for any other standalone app I install as well. Is this a bug in Chrome? Some obscure misconfigured setting?
If it is a bug, is there any workaround I can implement for my app?
Thanks for filing the bug. It should be fixed now:
https://chromium.googlesource.com/chromium/src/+/46fb0298b42b459bbc085c4b965a9fa4996d3e7c
Related
There are many (1 2 3) answers on Stackoverflow saying a Chrome extension cannot have rounded corners when opened, and yet... The 1Password extension does.
I've noticed the extension is draggable unlike other extensions, and I've noticed I can't right click and inspect it. I've also noticed that if I drag it very quickly, a 'ghost' extension flickers in the middle of my screen.
Any ideas whats going on?
What you're seeing is not part of the Chrome extension, but the 1Password application itself. The extension merely acts as a middleman between Chrome and the real password manager app on your computer. In fact, the 1Password extension requires the 1Password app to be installed on your computer in order to work. When you click on the icon, that's not a popup window, but a native window created by the 1Password app itself. This is done through native messaging.
I would love it if there was a hotkey, or some other method I could use to avoid having to use the mouse to constantly re-open this window whenever I redeploy my app.
Alternatively, is there a way of re-using an opened device inspector window that I'm unaware of?
chrome://inspect URL can be a good option.
But, what IS chrome://inspect? Well that's a global development tools page. It opens on the "Devices" tab by default, so that's handy.
I searched for a keyboard shortcut, but sadly I didn't discover any.
You could bookmark chrome://inspect and put a shortcut on your desktop by the way (except for Chromebooks, which is what I wrote my answer with)
From there, you can jump to inspection of any open page in your Chrome browser, which is nice too.
Alternative: When undocked, the Inspector will have the Console in the bottom. Well on the bar above the console, the leftmost three-dot menu has a direct "Devices Inspector" option.
I use os x and use Cmd+Opt+I Hotkeys to open Inspector in chrome.
You can find more hotkeys here
Hope this helps
Thanks
I am experiencing an issue with opening a Microsoft Office Document, using IT Hit WebDAV AJAX library, in latest Chrome 39.0. running on Windows OS. It is a sporadic issue that occurs only in Chrome, and it happens when one opens a document multiple times. Word instance won't start, the page freezes and browser becomes unresponsive, and Chrome suggests killing the page. The only solution is restarting the browser, which solves the issue.
I have tried opening a document in Chrome on Mac OS X, and it is working fine. So are Mozilla and Safari on all operating systems. It seems to be a Chrome + Windows issue only.
Has anyone experienced this issue and is there a fix?
The Microsoft Office plug-in that opens the document displays a warning popup "Some files can harm your computer.", which is a modeless dialog:
If you quickly click on a link that opens the document more than one time the dialog will hide behind the main web browser window. As a result the web browser window is blocked.
You need to switch to that dialog and confirm or reject document opening, otherwise after some time Chrome will ask you if to kill the page or wait.
Note that there is no way to avoid that dialog, this is a built-in MS Office functionality as far as I know.
Chrome will only work good with ITHitWebDAV if the user has got Office 2013 or superior.
Google is blocking all Java applets and NPAPIs now, so good luck with that. I just detect the browser of the user that wants to edit a document, and if it's chrome, I warn him to change to another browser like Firefox with a modal, and that's all.
Very poor support between Chrome and ITHitWebDAV, and no much you can do about it.
With Chrome 32.0.1700.77 the new emulator tab is handy except it's the default tab when I refresh my page.
During my standard development workflow, I constantly refresh the page when I make changes. I usually have the console window open at the bottom of the network or source views. But every single time I refresh the page, the Emulators tab takes focus and I can't see the console.
This is truly annoying since the app will fail because of a simple JavaScript typo, but I can't see the console without clicking one more time (to focus the console tab).
Has anyone found a workaround for this?
Combined with the Chrome Developer Tools unresponsive since update 32.0.1700.76 m issue, I would have to say Google really tripped up this release.
Unfortunately there doesn't seem to be a workaround yet. It looks like there has been a bug reported to Google as found on this thread, but no fix has come about yet.
I think the only way (right now) to prevent the console tab from being hidden when needed is to avoid using the emulator or revert to a previous version of Chrome.
Hopefully a fix comes soon!
It's been a while since this post was made, but I came across the same issue recently. When you have the developer toolbar open, the phone icon beside the "Elements" tab should be blue. Clicking that will disable Emulation.
source: https://groups.google.com/d/msg/google-chrome-developer-tools/g_93_bKmaiA/SdHk0aXdEo4J
I have the following issue:
When I load my flash app in Google Chrome everything works fine. But when I switch to another tab in browser, wait a bit and switch back instead of my flash app I see white area. Moreover, when I do right-click on it I see flash menu (that one you normally see on right-click).
I see this strange issue only in Google Chrome.
I have Google Chrome 19.0.1084.56 and it runs on Mac.
Any ideas and thoughts are welcome!