Closed
Bug 1378447
Opened 7 years ago
Closed 1 day ago
Arrow buttons misaligned on mobile view of msn.com
Categories
(Core :: Layout, defect, P3)
Core
Layout
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: dholbert, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(2 files, 1 obsolete file)
Filing this for https://github.com/webcompat/web-bugs/issues/7615 Steps to Reproduce 1. Navigate to: http://www.msn.com/en-us/money/spending 2. (optional) Tap “Next” button on second menu bar 3. Observe “Next/Prev” buttons layout. Expected Behavior: Buttons are correctly aligned on the menu bar (vertically centered, aligned with text) Actual Behavior: Buttons are misaligned.
Reporter | ||
Comment 1•7 years ago
|
||
Reporter | ||
Comment 2•7 years ago
|
||
Comment on attachment 8883637 [details]
testcase 1 (partially reduced)
With this testcase, Chrome renders the "AAA" and "BBB" text at approximately the same Y-position (a few pixels difference, but not much).
Firefox renders "AAA" and "BBB" on completely different lines.
Attachment #8883637 -
Attachment description: testcase 1 (paritally reduced) → testcase 1 (partially reduced)
Reporter | ||
Comment 3•7 years ago
|
||
Edge 15 matches Chrome's rendering, FWIW.
Keywords: testcase
Whiteboard: [webcompat]
Reporter | ||
Comment 4•7 years ago
|
||
Reporter | ||
Updated•7 years ago
|
Attachment #8883643 -
Attachment description: testcase 2 → (testcase 1.9 - ignore)
Attachment #8883643 -
Attachment is obsolete: true
Reporter | ||
Comment 5•7 years ago
|
||
On testcase 2: - Firefox aligns the "Am I snapped..." text with the center of the buttons. - Edge + Chrome instead push the "Am I snapped..." text with the bottom of the buttons. Firefox is probably deriving the button's baseline from its internal button-contents wrapper-box (which is vertically centered), whereas Chrome and Edge are deriving it from the button's border. (This discrepancy only matters for buttons that have no contents [or only abspos placeholders as their contents]. For buttons that have text inside of them, everyone agrees that the button-text's baseline should be used as the button's baseline.)
Updated•7 years ago
|
Priority: -- → P3
Reporter | ||
Updated•7 years ago
|
status-firefox57:
--- → wontfix
Comment 6•5 years ago
|
||
Migrating Webcompat whiteboard priorities to project flags. See bug 1547409.
Webcompat Priority: --- → ?
Comment 7•5 years ago
|
||
See bug 1547409. Migrating whiteboard priority tags to program flags.
Updated•5 years ago
|
Webcompat Priority: ? → P3
Updated•2 years ago
|
Severity: normal → S3
Comment 8•1 day ago
|
||
This doesn't appear to be an issue anymore. Firefox, Chrome, and Safari render the text similarly on different lines now, and MSN's layout has since changed and no longer has this issue.
Status: NEW → RESOLVED
Closed: 1 day ago
Webcompat Priority: P3 → ---
Resolution: --- → WORKSFORME
Whiteboard: [webcompat]
You need to log in
before you can comment on or make changes to this bug.
Description
•