We have an application we currently run in Chrome browser on Ubuntu and Windows using PrintNode. We'd like to run our application ChromeOS to move away from Linux and Windows, but our the printing of our app requires no user interaction. It appears Chrome browser on Chrome OS forces a Print Dialog/Prompt to the user to confirm the print job. Does anyone know how to suppress this? In the past on Windows/Linux we've leveraged "--kiosk-printing" in Chrome through properties of the desktop shortcut, but this doesn't appear to be possible in the browser in ChromeOS.
Does anyone have an ideas on how to bypass the print dialog in ChromeOS?
Related
I'm new to Cypress and recently started implementing e2e tests for our system. A peculiarity of this system is that the authentication happens on a popup window.
I've already successfully created a simple test that loads the site, waits for the authentication to complete and then asserts that the page title is shown. This test runs without errors using the cypress client (cypress open), but when I run it in headless mode (cypress run --headless) the test fails.
When I see the video from the headless run, I don't see the popup window appear like it does when I run it with the GUI. Has anyone else had an issue like this where popup windows don't show on headless mode?
I also found this bug on the Chromium site related to issues displaying popup windows in headless mode, so it might be related to that, but the bug appears as closed.
I'm using Cypress 6.1.0 and Chrome 87
Thanks in advance for any help.
This was being caused by an issue with the integration of my website with another service that for some reason only occurred on headless mode. After fixing that, it works ok.
we have an C# backend that launches and integrates with a chrome webapp in kiosk mode. we have a message that is executed from webapp that tells the backend to close chrome and show the backend ui (a service ui).
This works fine, but we are using Process.Kill to close chrome. We've got other issues that we believe that may be related to left overs from the harsh closing of chrome.
What is the proper way to close chrome, once Kiosk mode has been entered?
I noticed that recently Chrome started blocking flash on a site even when it's manually allowed in the site settings. Probably something has been changed in security policy last days? I completed all steps desribed on Google Chrome Help and still have no luck.
I'm running Windows 10, Google Chrome Version 60.0.3112.78 (Official Build) (64-bit)
Try:
Launch chrome
Navigate to chrome://flags/#prefer-html-over-flash
The flag is most likely set to Default
Change the flag to Disabled
Relaunch Chrome
Does Flash content display now?
I have a packaged app that calls chrome.runtime.reload(). On a desktop OS (Windows, OSX) this call will cause the application to close, but not restart unless there is an additional Chrome page open.
I assume this is because if it is the only Chrome app running, it closes the Chrome process entirely and there is nothing to restart it.
Adding the background permission looks like it should work, according to the documentation but it does not seem to actually start Chrome when the user logs in (and keep it running) as the documentation states.
A user can override this globally with a setting.
In Chrome's settings with "Show advanced settings":
System > Continue running background apps when Google Chrome is closed
Perhaps it is disabled on your development system.
I have a weird situation here. I have an Amazon EC2 instance running Windows Server 2012. I installed Google Chrome on the volume. Everything works fine but one very annoying thing. When I'm using Google Chrome if I click on the address bar or any text input Windows Explorer pops up to a folder with the path C:\Program Files(x86)\Google\Chrome\Application\XX.XX.XX.XX\ (these X's seem to be in the format of an IP address). Has anyone else ran into this and if so what is going on and is there a fix? Everything works fine, but it's just annoying me for this window to pop up. Thanks