I have been working on a chrome packaged app, which requires desktopCapture permission from the user. The window size of the app is fixed. The issue is when the user opens the app he is asked to grant permission for sharing his screen. The popup appears just fine on other OS's other than Windows. In case of Windows the popup is clipped in half (please see the attached image).
Can any one help please.
http://i.stack.imgur.com/ZMPDm.jpg
Do you mind filing a bug at http://crbug.com/new so that the chromium team cam have a look? It is definitely a bug.
Related
General Problem
We've had a long-standing problem with our two ExtJS 5.1.0 apps that div scrollbars don't show in Chrome, using only our QA testers' AWS Workspace Chrome browsers. They don't see this in other websites using that Chrome, only our two applications. We've been able to ignore this since the problem was isolated, but now a user is having the same problem.
We've been able to confirm that the difference is that wherever there's a div that should be overflow: auto is being generated as overflow: hidden. So scrollbars for grids, dropdowns, etc don't render but the div can still be scrolled via other means (tabbing, page down).
I've been looking for general ideas about what could cause this--is it ExtJS? Windows setting? Chrome setting? Again, the problem is isolated to AWS Workspace's Chrome and a user's Chrome.
Versions
Chrome:
AWS Workspace has exact same Chrome version as me, 79.0.3945.88.
User has Chrome 80.0.3987.149 (up-to-date).
Windows:
AWS Workspace is Windows Server 2016 Datacenter.
User has Windows 10.
What We've Tried
These are all troubleshooting steps we've tried in the AWS Workspace Chrome:
Disabled all extensions. Also ran in incognito mode which should do this also. The extensions are nothing that I don't also have, and I don't see the problem.
Inspected Chrome's flags--they're all default, and again not different than what I have.
Disabled Chrome's “Use hardware acceleration when available” setting and restarted Chrome.
Previously opened a ticket up with AWS and they were unable to help.
Researched any connection of this to Chrome, ExtJS, or Windows Server 2016 Datacenter without luck. Only found general information about "what to do if you have scrolling problems in Chrome".
Other Problems Our Apps Have in AWS Workspace Chrome
Listing these in case it helps trigger any ideas about the underlying problem, but focusing on the scrolling for now. Again these are isolated to Chrome in AWS Workspace (unclear if the user is seeing these also):
Drag and drop doesn't work.
Tabs that aren't the selected tab when the tab bar is loaded don't load at all.
It turns out that the problem was related to touchscreens. Our user has a touchscreen laptop (and didn't realize it for a while, we asked about this early on). And the Amazon Workspaces are touchscreen-compatible, as they have a "HID compliant touch screen" device listed in Device Manager > Human Interface Devices. So something about touchscreens + Chrome/Edge is telling ExtJS 5.1.0 that the device is mobile and scrollbars shouldn't be rendered.
Solutions:
For our user, she was happy to disable her touchscreen device and this worked for her.
For Amazon Workspaces, disabling the touchscreen device did not work. For Chrome we were able to resolve by adding --touch-events=enabled to the Chrome shortcut. There are various touch-related Chrome flags mentioned online as a solution, but none of those are available in the current version. Anything touch-related we did find in Chrome's list of flags didn't help.
I haven't looked for a solution for Edge if someone uses Edge and wants to keep their touchscreen. This is fine for us right now. (Because we realized Edge has the problem also, presumably due to Chromium. Did not see it with Firefox.)
And I did confirm using ExtJs' Kitchen Sink examples that I can replicate the problem in 5.1.0 with both a touchscreen laptop and an Amazon Workspace. Also that I can't replicate the problem in the current version, so we should be good once we upgrade.
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 use the Chrome in my laptop with Windows 7 OS, and the Chrome on Windows provides a Device Mode(shortcut is F12) so that it can simulate a specific mobile device to get and display a Web page in a Chrome tab as follow.
However, such Device Mode is only limited on a single Chrome tab, so when you close the tab and open a new one, the new tab get and show the web page as normal, not as in the Device Mode.
So my question is How to set the Device Mode permanently, and when I open a new tab in the Chrome, it runs on Device Mode by default. Is there any method or plug-in can help me to achieve it?
I believe that this is not applicable as Google created that mode for inspection purposes only not for navigating or viewing.
So you will need a smartphone simulator like the one which is provided by Android SDK or the IOS simulator which comes with XCODE on mac, or you can use a real smartphone of course, and you can inspect on it via your PC using ADOBE Edge Inspect extension on chrome.
Chrome inspector mode is designed with testing in mind, and isn't intended for regular browser use. You might try a device simulator tool, like what's included in Xcode or Eclipse IDE.
Hope this helps.
I think this is something what you are looking for
Google chrome plugin
You can open devtool automatically with chrome switches, so i suppose that you can reach your goal with the correct one... our only problem is that chrome's switches are thousands... that's the documentation, good reading :D (unofficial documentation here)
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.
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