I am running Chromium in kiosk mode:
chrome.exe --kiosk http://127.0.0.1:1234/
for an embedded (desktop) computer, which a touch monitor only (no keyboard, no mouse).
Is there a way to configure desktop Chromium to behave like a mobile/touch UI?
More precisely, how to make that when clicking/touching a HTML <input> element, an on-screen keyboard similar to the one displayed on Chrome for Android is automatically displayed?
Note: I'd like to do this directly at Chrome level, and, if possible, avoid to use a third-party extension like Virtual Keyboard or a JS library like this one.
Adding these extra chrome flags used to work previously, however I cannot confirm as I do not have a touchscreen monitor at the moment:
chrome.exe --kiosk --touch-events -enable-viewport http://127.0.0.1:1234/
Also you may want to consider the following, it may also apply to Chromium: Disable Chrome pinch zoom for use in kiosk
For anyone reading in 2022 - those flags does not open on screen keyboard (tested on touchscreen monitor)
Related
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)
We are trying to run some automated tests (coded ui based) on our mobile application via Chrome browser.
In order to make the tests available to run, we must set the browser to work as 'emulate touch events'.
The thing is that as part of our test flow, a new chrome browser is being launched on each test but the definition is gone.
I already check this one, but it doesn't work:
How to Always Emulate Touch Events in Chrome Dev Tools?
Any other suggestions?
Thanks,
Yair
I believe that the dev tools window must be opened for the overrides to kick in, have you tried that?
I need to run the touch based browser app in my desktop and modify some codes written in touch events. Can some one tell me what are the best ways to run the touch screen apps in non touch environment? and check its event?
If your app is running inside a browser, you can emulate touch events on non-touch systems by turning on touch emulation in Chrome's developer tools.
In Chrome 26+ this can be found by clicking the "gear wheel" icon in the bottom right, and then selecting the "Overrides" panel. See https://developers.google.com/chrome-developer-tools/docs/mobile-emulation#emulate-touch-events
NB: this will only work while the DevTools are open. So it should be fine for testing, but not for end-user running.
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
Is it possible to resize the Chrome window using the developer tool's console? If so, what would the command be? becuase the window.resizeTo(w,h) didn't work for me.
Official Chrome issue says:
By Design we don't support resize/move for tabs, only constrained windows.
Windows in Chrome can be resized via Chrome extensions API, however it's not available from console. You should probably try using one of many 'window resizing' extensions. In the near future it will be possible for extensions to add own console commands, however as for now it's an experimental feature.
i think you can only resize windows that's you have created from the console, like popups
for example:
var pop=window.open("","","width=1024,height=768");
pop.resizeTo(100,100);
On macOS you can run: open -a Google\ Chrome --args --window-size=1366,768
Since Firefox 7, it's no longer possible for a web site to change the default size of a window in a browser, according to the following rules:
You can't resize a window or tab that wasn’t created by window.open.
You can't resize a window or tab when it’s in a window with more than one tab.
found on https://developer.mozilla.org/en-US/docs/DOM/window.resizeTo#Notes
some try and error seems to prove that these rules also apply in Chrome.