Open Bug 1298064 Opened 3 years ago Updated 2 years ago

Container tab menu on long press add menu not present after customize


(Core :: DOM: Security, defect, P3)

53 Branch



Tracking Status
firefox50 --- unaffected
firefox51 --- unaffected
firefox52 --- affected
firefox53 --- affected
firefox57 --- fix-optional


(Reporter: jkt, Assigned: jkt)


(Blocks 1 open bug)


(Whiteboard: [domsecurity-active][userContextId])

After the longpress button goes live there is a follow up issue that once the user customises the browser to not have the add button; placing it back would not have the long press functionality.
Whiteboard: [domsecurity-active][userContextId]
Priority: -- → P3
jkt, is this still valid?
Flags: needinfo?(jkt)
I don't think this is an issues anymore. I went through the test cases listed below on all three platforms and I couldn't reproduce the original problem.

Hopefully one of the cases listed below was the one that Jonathan was originally running into.

Test Cases Used:

* moving the new tab button (+) into the hamburger menu and than moving it back to the original location
* moving the new tab button (+) into the customization window and than moving it back into the original location
* moved the new tab button (+) into other locations
* ensured that the new tab button (+) is still working after using "Restore Defaults"

Platforms Used:

* macOS 10.12.1 x64 - PASSED
* Win 10 x64 VM - PASSED
* Ubuntu 16.04 x64 VM - PASSED

Build being used:
I think the bug is related to Bug 1317317 but I'm not sure that will fix it.

To my understanding the STR would be:
- disable containers
- drag new tab to customise window
- enable containers
- drag back out
- container menu won't be present as it's added only if it is present in the browser when enabled
Depends on: 1317317
Flags: needinfo?(jkt)
Thanks Jonathan, I can reproduce this on both fx53 and fx52 on all the current platforms using the STR from comment#3.
OS: Unspecified → All
Hardware: Unspecified → All
Version: unspecified → 53 Branch
Assignee: nobody → jkt
You need to log in before you can comment on or make changes to this bug.