New issue
Advanced search Search tips

Issue 658512 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

The infrared-to-tube touchscreen device has no event response

Reported by jirih...@gmail.com, Oct 22 2016

Issue description

Chrome Version: <From about:version: Google Chrome 53.0.2785.154>
Chrome OS Version: <From about:version: Platform 8530.96.0>
Chrome OS Platform: <asus/C100PA-DB02 of computer running Chrome OS>
<b>Network info: <network, encryption type, router model (if known)></b>

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1)First of all, our company's infrared touch screen is transmitted through the USB data, and the device is free drive, just like the mouse, keyboard.At the same time, our devices support multi-touch.Connected to the Windows system, the same as the operation of mobile phone screen.
(2)Our touch-screen devices are not supported on all Chromebooks, and there is no corresponding event response to the touch-sensitive box. For example, on Windows, I click the touch box and the cursor changes to a small dot.
(3)Because Chrome OS kernel is Linux 3.14, based on the function of linux input subsystem, I use the command: cat dev / input / event5 | hexdump, crawl asus C100PA-DB02 chromebook capacitive screen click event data, the data is Input subsystem under the event data, and then I will be our company's devices connected to the Chromebook via USB to the same method and operation to capture the same event data, comparing the two data did not find any similarities and differences.But the Chromebook can perfectly support the operation of the capacitive screen, for example, through the capacitive screen can be drawn in the chrome browser drawing plug-in, you can capacitive screen to open the application and other related operations. However, these things our device does not work on the chromebook at all.What's wrong?
(4)The same data, why the capacitive screen will respond and our products do not respond?
Expected Result:So that our device can be as capacitive screen that can operate on the chromebook.

(5)Thank you for your answer!

Actual Result:The underlying data has, but the upper application does not seem to support

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always!

What is the impact to the user, and is there a workaround? If so, what is
it?

Please provide any additional information below. Attach a screen shot or
log if possible.


 
Two touch screen data.rar
8.6 KB Download

Comment 1 by rung70...@gmail.com, Oct 23 2016

Screenshot_2016-10-24-05-04-35.png
127 KB View Download

Comment 3 by vsu...@chromium.org, Jan 26 2017

Components: Internals>Input
Project Member

Comment 4 by sheriffbot@chromium.org, Feb 13 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment