Open
Bug 1428602
Opened 7 years ago
Updated 3 years ago
Add-on content container layout is broken when install first add-on
Categories
(Toolkit :: Add-ons Manager, defect, P3)
Toolkit
Add-ons Manager
Tracking
()
REOPENED
| Tracking | Status | |
|---|---|---|
| firefox-esr52 | --- | unaffected |
| firefox-esr60 | --- | wontfix |
| firefox57 | --- | unaffected |
| firefox58 | --- | unaffected |
| firefox59 | --- | wontfix |
| firefox60 | --- | wontfix |
| firefox61 | --- | fix-optional |
| firefox62 | --- | fix-optional |
People
(Reporter: magicp.jp, Unassigned)
References
Details
(Keywords: regression)
Attachments
(2 files)
Steps to reproduce:
1. Launch Nightly with a new profile
2. Open about:addons
3. Select "Extensions" category
4. Install any add-ons
e.g. Search "mozilla container"
Install "Firefox Multi-Account Containers"
Close "Firefox Multi-Account Containers" page
Actual results:
Add-on content container layout is broken. It will work after refresh the page.
Expected results:
Correct layout.
Regression range:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=cd942db65cf93dad9688937034ef7f8fb91e5379&tochange=2297e770f16c7411ff64dce3349a9406a59a9129
Blocks: new-amo-search
Has Regression Range: --- → yes
Has STR: --- → yes
status-firefox57:
--- → unaffected
status-firefox58:
--- → unaffected
status-firefox-esr52:
--- → unaffected
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
It has not been fixed in 1424909. Please find the expected image.
Assignee: nobody → magicp.jp
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
status-firefox60:
--- → wontfix
status-firefox61:
--- → affected
status-firefox62:
--- → affected
status-firefox-esr60:
--- → wontfix
Updated•7 years ago
|
Keywords: regression
Comment 4•7 years ago
|
||
Yeah, not a duplicate. magicp you assigned the bug to yourself, are you working on a fix?
Flags: needinfo?(aswan)
Priority: -- → P3
Updated•7 years ago
|
Assignee: magicp.jp → nobody
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•