Closed
Bug 2082394
Opened 1 month ago
Closed 6 days ago
[customizable menu] Support using the default or custom menu strucutre when building the browser menu
Categories
(Firefox for Android :: Menu, task)
Tracking
()
RESOLVED
FIXED
162 Branch
| Tracking | Status | |
|---|---|---|
| firefox162 | --- | fixed |
People
(Reporter: petru, Assigned: petru)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxdroid][android-core])
Attachments
(1 external file)
When building the browser menu Fenix should check if a custom configuration exists and use that instead of the default for what to show to the users.
Updated•1 month ago
|
| Assignee | ||
Updated•15 days ago
|
Assignee: nobody → petru
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•15 days ago
|
||
The customization was read only after the first page was drawn, so a
browser menu opened before that showed the default structure instead of
the one the user customized. When the menu can be customized, its items
are now built only once the customization was read, which the menu
already waited for to show them.
Pushed by plingurar@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/a97e59c35f55
https://hg.mozilla.org/integration/autoland/rev/b22ec2bdb098
Build the browser menu from the custom or default structure once the customization is read r=android-reviewers,giorga
Comment 3•6 days ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 6 days ago
status-firefox162:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 162 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•