"Open Pop-up Windows" site permissions' drop-down list items are too narrow
Categories
(Firefox :: Site Permissions, defect, P3)
Tracking
()
People
(Reporter: cpeterson, Assigned: aarushivij)
References
Details
(Keywords: regression)
Attachments
(4 files)
Comment 1•7 years ago
|
||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 3•5 years ago
|
||
Hello, can I work on this?
I can reproduce the issue on linux too. (Dropdown has different width compared to header)
Do I need to make drop down's list item width equal to lists header?
Thanks
Aarushi :)
Comment 4•5 years ago
|
||
I'm not proper person to fully answer this question, so I'm redirecting it Johann Hofmann [:johannh].
Assignee | ||
Comment 5•5 years ago
|
||
Hello Johann ,
I was trying to fix the bug.
Is it how it should look?
Shall push the patch once confirmed by you :)
Thanks
Comment 6•5 years ago
|
||
Yeah, that's about how I would expect things to look, though I guess it depends on the approach :)
Thanks!
Assignee | ||
Comment 7•5 years ago
|
||
Okay, Thanks Johann
Shall push the patch :)
Assignee | ||
Comment 8•5 years ago
|
||
Updated•5 years ago
|
Comment 9•5 years ago
|
||
Hello, this bug does seem to be a regression, as the first builds in which the drop-down was implemented it looked okay, soon after though the drop-down elements changed to the more narrow version. I've tried to find a specific build using mozregression but it seems it can't reach all the builds, however, this is what I've found:
last known good build: 2017-10-26 pushlog
first known bad build: 2017-10-27 pushlog
Updated•5 years ago
|
Updated•5 years ago
|
Comment 10•5 years ago
|
||
(In reply to Daniel Kolsis from comment #9)
[...] first known bad build: 2017-10-27 pushlog
For this regression changelog, bug #1411290 looks most suspicious.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 11•5 years ago
|
||
Comment 12•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•5 years ago
|
Comment 13•5 years ago
|
||
Reproduced the issue using Firefox 60.0a1 (20180302220122) on Windows 10x64.
The issue is verified fixed with Firefox 76.0b4 (20200412214314) on Windows 10x64 and ubuntu 18.04.
Description
•