killing the Chrome process after 5 seconds by the same start up script.Starting Chrome 35 automatically by startup script.Setting the -touch-events=enabled flag, as suggested in Chrome + Touchscreen + Unity (14.04) or Ubuntu 14.04 multi touch screen support, does not work. But chromium-browser remained at version 34 and still accepts touch events, so it is rather a Chrome 35 issue.
Maybe that is not a Chrome issue, as I ran a system update via the packet manager. If I close Chrome and restart it again, touch events will work fine, as well as on system buttons like refresh as on HTML pages. It is not just a HTML or CSS issue, as I can move the then invisible mouse cursor on Chrome system buttons as the refresh button or the url bar and no click event takes place, but according hints are shown. Touch events worked fine with Google Chrome 34, but are broken after the update. 114 on Ubuntu 14.04, Chrome does not respond to touch events anymore at a first start.Ĭhrome is invoked at start up via a script by calling google-chrome After updating Chrome to Version Google Chrome.
0 kommentar(er)
