Hello CentBrowser team,
since Chrome 49, Google has decided, again, to put some weird features without asking users. This time, it affects people (like me) using hybrid laptops (like the Asus Transformer book).
Before : when pressing an input field (like the address bar, the search engine, etc.) with a finger on the tactile screen, the virtual keyboard automatically opens, even if a keyboard is connected. So we can use both the tactile screen AND the keyboard.
Now : since Chrome engine 49, it doesn't work anymore. The virtual keyboard does not appear automatically, and we must add some command-line to remove this strange behavior (thankfully, you have added command-line option in CB) :
--disable-usb-keyboard-detect
Is there a chance to add an option (without a command-line) in next CB builds to allow users to disable that "feature" (which I prefer to qualify as a bug
) ? or maybe even totally remove it from CB ? I really don't understand Google's choice this time...
Thanks for reading.
since Chrome 49, Google has decided, again, to put some weird features without asking users. This time, it affects people (like me) using hybrid laptops (like the Asus Transformer book).
Before : when pressing an input field (like the address bar, the search engine, etc.) with a finger on the tactile screen, the virtual keyboard automatically opens, even if a keyboard is connected. So we can use both the tactile screen AND the keyboard.
Now : since Chrome engine 49, it doesn't work anymore. The virtual keyboard does not appear automatically, and we must add some command-line to remove this strange behavior (thankfully, you have added command-line option in CB) :
--disable-usb-keyboard-detect
Is there a chance to add an option (without a command-line) in next CB builds to allow users to disable that "feature" (which I prefer to qualify as a bug
) ? or maybe even totally remove it from CB ? I really don't understand Google's choice this time...Thanks for reading.