navigator.maxTouchPoints returns 0 in child process
Categories
(Core :: DOM: Content Processes, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: smaug, Assigned: smaug)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file, 1 obsolete file)
...but it returns the right value in parent process, if one is using touch screen.
https://patrickhlauke.github.io/touch/tests/pointer-multitouch-detect.html
Assignee | ||
Comment 1•6 years ago
|
||
well, this isn't really bug 822898 related, but later regression.
Comment 2•6 years ago
|
||
(In reply to Olli Pettay [:smaug] from comment #1)
well, this isn't really bug 822898 related, but later regression.
e10s support was added by bug 1137555. But it seems to be broken at 2017/05 (we cannot use mozregression for older build). I suspect bug 1347035...
Comment 3•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 4•6 years ago
|
||
Assignee | ||
Comment 5•6 years ago
|
||
Adding two tests, browser-chrome test to test this bug that a newly opened tab gets the right
maxTouchPoints, and another test for window.open case to ensure we don't regress that case either.
Assignee | ||
Comment 6•6 years ago
|
||
This is a regression from bug 1347035.
We don't have very nice way to pass this kind of data around, at least not yet. Fission may make this simpler.
The patch makes TabContext to know the number of points, and BrowserChild happens to extend that class, so we can remove the getter/setter from BrowserChild.
Updated•6 years ago
|
Assignee | ||
Comment 7•6 years ago
|
||
And need to merge to new staticprefs syntax
Assignee | ||
Comment 8•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 10•6 years ago
|
||
bugherder |
Updated•4 years ago
|
Description
•