Closed Bug 1298982 Opened 9 years ago Closed 9 years ago

[e10s] Unable to make pinned tab using finger on touch-enabled screen

Categories

(Firefox :: Tabbed Browser, defect)

51 Branch
x86_64
Windows 10
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
e10s + ---

People

(Reporter: Abe_LV, Assigned: kats)

References

Details

Mozilla/5.0 (Windows NT 10.0; rv 51.0) Gecko/20100101 Firefox/51.0 [Pre-Requisites] touch screen laptop/surface pro about:config settings: javascript.options.asyncstack; false browser.tabs.remote.force-enable; true layers.async-pan-zoom.enabled; true about:support shows Multiprocess Windows 1/1 (Enabled by user) about:support Asynchronous Pan/Zoom wheel input enabled; touch input enabled [Steps to Reproduce] 1.On touch enabled laptop open new tab 2.Using your finger press and hold on the tab until a menu pops up. 3.Select "Pin Tab" if the menu is still displayed [Expected Results] User should be able to make pinned tab on touch enabled screen laptops using finger [Actual Results] The pop-up menu disappears before user selects the "Pin Tab" option. [Note] This only happens when e10s is enabled.
tracking-e10s: --- → ?
Flags: needinfo?(bugmail)
Thanks, this is likely the same underlying issue as bug 1292572. I plan on fixing that in the next few days, parking this with me for now.
Assignee: nobody → bugmail
Depends on: 1292572
Flags: needinfo?(bugmail)
Version: 49 Branch → 51 Branch
On touch enabled screen this issue is not reproducible with the latest nightly build: 20160901030202. User Agent Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
The backout in bug 1298313 should have fixed this, and the patches in bug 1298908 should have improved things. Resolving.
Status: NEW → RESOLVED
Closed: 9 years ago
Depends on: 1298908, 1298313
No longer depends on: 1292572
Resolution: --- → FIXED
Verified as fixed with latest nightly. -- Version 51.0a1 Build ID 20160902030222 Update Channel nightly User Agent Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0
You need to log in before you can comment on or make changes to this bug.