I need print receipt in Chrome running in
--kiosk
mode. Of course I use
--kiosk-printing
to disable print dialog. I have to note this parameter only emulate automatic pressing Print button.
My printer is Rongta RP80 80mm Thermal Receipt Printer connected via USB to laptop with Windows 10, Chrome 57.
Printing mechanism is easy, printing launches by javascript on page.
When I don't use --kiosk-printing parameter printing starts immediately on Print button press in chrome print preview dialog.
I face to big problem with --kiosk-printing: printing starts only after 1-2 minutes since chrome printing dialog appear and disappear (as noticed, parameter only emulate automatic pressing Print button). It is not printer problem, cause new document appear in windows print queue after this lag.
Why there is a so big lag with --kiosk-printing parameter, how to minimize it?
I had the same problem here when I upgrade chrome to version 57 recently. The only solution at the moment is install an older version of chrome. http://www.geocities.jp/ecvcn/exam/chrome_installer.html
I had the same problem. Using Chrome Canary on a Windows 8.1 PC solved it for me.
mee too, but normal is quite slow, sometimes it not print anything... not only on --kiosk --kiosk-printing. after using Vivaldi (fork of
I had the same problem in April, same in canary, users report that it's fixed in 58 (stable), just update chrome (in help menu, about Google chrome) :
https://bugs.chromium.org/p/chromium/issues/detail?id=706180
So the bug is fixed now.
In the Google Chrome browser property:
-kiosk --disable-print-preview
This will remove your pain.
Related
I am running Node.js on localhost:3001 and unintentionally wrote some code with an infinite while loop. This locked up Chrome to the point where the only resolution was to kill the browser. Since then, I found the problem in my code using Firefox, and fixed the code, but even after restarting Chrome, it will not load my page. I even changed the port that the server runs on, and the cache is disabled with developer tools open - Chrome simply refuses to load the page. I see a single request to the server for the page, but in Chrome it just registers as Pending.
Has Chrome maybe flagged this page as suspect, somehow? How do I get it to play again? I would at least expect Chrome to offer some opportunity to kill a tight loop - like Firefox does - but I've yet to see it. Is there some setting I can tweak? I'm on version 74.0.3729.169 (Official Build) (64-bit), although now that I opened the About page, I see that it is updating Chrome, so maybe that will fix it.
UPDATE: It didn't fix it, but it works in Incognito mode. ???!!!
UPDATE: Disabling all of my extensions also didn't fix it!
I found a setting in Chrome: "Continue to run background apps when Chrome is closed"
I turned that off, and now it works again.
The chrome tabs auto refreshes every time when I go to the tab and its turning out to be really annoying. Any fix?
I was able to resolve this inside Chrome Version 48.0 (Running on Windows 7) by performing the following steps.
1.) Open the Chrome browser and navigate to chrome://flags
2.) Search on the page for "Enable tab discarding"
3.) Set this flag to "Disabled"
4.) Restart Chrome.
Chrome will do that when you are low on memory. If you have a lot of programs open, try closing some of them out.
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
Every browser that I have tried has the following feature: When you click in a text input field the virtual keyboard symbol is revealed below the text input field (when using a touch screen in windows 7). All browsers except chrome. Anyone knows why and have a possible sollution? (Image below is from Internet explorer)
I would like to test a prototype using touch gestures that only works in chrome thats why I would like to use that browser and that browser alone. =)
Best extension for Chrome is Google Input Tools (made by google)
Found my preffered sollution to my problem using this program hot virtual keyboard
http://www.youtube.com/watch?v=vcYEFk6_5GQ
I'm currently using this Chrome extension in kiosk mode to show a virtual keyboard when focusing inputs. This is the "less worse" I found. I'm also using this one to enable touch gestures.
has anybody luck with a virtual keyboard that works inside an iframe? Nothing I tested worked with 16.04. Even with chrome web security disabled
There is an extension for Google Chrome:
https://chrome.google.com/webstore/detail/tippopper-extension/colobklhibekgdbeplpjchcgpagefagn