panel-list items in the migration wizard are vertically misaligned
Categories
(Firefox :: Migration, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox150 | --- | unaffected |
| firefox151 | --- | fixed |
| firefox152 | --- | fixed |
People
(Reporter: mconley, Assigned: dao)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, Whiteboard: [sng][mcab-hnt])
Attachments
(4 files)
I noticed this today, and it's a fairly recent regression.
15:32.82 INFO: Last good revision: 0b16302a254fb31bd65ec6bdeac410878983aeb1
15:32.82 INFO: First bad revision: f8622fd9691adc745836f73c2f7f476245a16f82
15:32.82 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=0b16302a254fb31bd65ec6bdeac410878983aeb1&tochange=f8622fd9691adc745836f73c2f7f476245a16f82
STR:
- Go to about:settings#general
- Click "Import data"
- Click on the browser / profile selection dropdown
ER:
The list of browsers and profiles that we can import from should be vertically aligned in the middle.
AR:
The list of browsers and profiles that we can import from appear to be too high up, vertically. See screenshot.
| Reporter | ||
Comment 1•1 month ago
|
||
| Reporter | ||
Comment 2•1 month ago
|
||
Comment 3•1 month ago
|
||
Set release status flags based on info from the regressing bug 2033862
:dao, since you are the author of the regressor, bug 2033862, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Comment 4•1 month ago
|
||
| Assignee | ||
Comment 5•1 month ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D296932
Updated•1 month ago
|
Comment 6•1 month ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: See https://bugzilla.mozilla.org/show_bug.cgi?id=2035009#c1
This is a regression from https://bugzilla.mozilla.org/show_bug.cgi?id=2033862 which is needed in 151.
It's strictly a cosmetic issue but looks broken enough that we shouldn't ship with this if possible.
- Code covered by automated testing?: no
- Fix verified in Nightly?: no
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: Trivial fix.
- String changes made/needed?: none
- Is Android affected?: no
Comment 8•1 month ago
|
||
| bugherder | ||
Updated•1 month ago
|
Updated•1 month ago
|
Description
•