Closed
Bug 1499344
Opened 6 years ago
Closed 1 year ago
Touchscreen is incorrectly recognized on Microsoft Surface Pro 2 i5
Categories
(Core :: Layout, defect, P3)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox64 | --- | affected |
People
(Reporter: danibodea, Unassigned)
References
Details
[Note]:
- A touchscreen is recognized by the test page even if it is disabled.
[Affected versions]:
- v64.0a1
[Affected platforms]:
- Windows on Microsoft Surface Pro 2 i5
[Steps to reproduce]:
1. Enable the touchscreen of the touchscreen capable device, tutorial here:
https://support.microsoft.com/en-us/help/4028019/windows-enable-and-disable-your-touchscreen-in-windows-10
2. Disconnect any other pointing devices.
3. Open browser and open test page:
https://hiikezoe.github.io/interaction-media-features.html
4. Leave the test page in view and disable the touchscreen from the Device Manager.
[Expected result]:
- Test page content shows:
pointer: none
any-pointer: none
hover: none
any-hover: none
[Actual result]:
- Test page content shows:
pointer: coarse
any-pointer: coarse
hover: none
any-hover: none
[Additional notes]:
- This tablet is a Microsoft Surface Pro 2 i5:
Name: DESKTOP-SE83IIG
Serial number: 019373535253
SKU: Surface Pro 2 i5
Version Information
Embedded controller: 24.1.50.0
System aggregator: 2.4.450.0
UEFI: 2.5.250.0
Wi-Fi driver: 14.69.24054.176
- In the Device Manager of the Surface Pro 2, the "Intel(R) Precise Touch Device" device does not appear, like in the case of the Surface Pro 4;
- To disable the touch screen, I can only disable the "HID-compliant touch device" device, in which case, the "HID-compliant mouse" device would not disappear, unlike in the case of the newer Surface Pro 4.
Comment 1•6 years ago
|
||
Thanks for filing this.
As discussed on Slack, I don't think this is a blocker for Firefox 64, setting P3 at this moment.
I guess this is somewhat related to bug 1498286, we need a reliable way to tell there is no touchscreen.
Priority: -- → P3
Updated•6 years ago
|
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
Comment 2•1 year ago
|
||
This was fixed in Bug 1813979
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•