Closed
Bug 957746
Opened 11 years ago
Closed 11 years ago
[B2G][Facebook] Profile picture misaligned in comments of a status
Categories
(Tech Evangelism Graveyard :: Preinstalled B2G Apps, defect, P3)
Tracking
(b2g18 affected, b2g-v1.2 affected, b2g-v1.3 affected)
RESOLVED
WORKSFORME
People
(Reporter: jschmitt, Assigned: colby)
References
Details
(Whiteboard: dogfood1.3)
Attachments
(1 file)
51.51 KB,
image/png
|
Details |
Description: Profile pictures are not aligned correctly within the comments section of a status Repro Steps: 1) Updated Buri to BuildID: 20140106004001 2) Download the 'Facebook' app from the Marketplace 3) Load the 'Facebook' app 4) Sign into an account 5) Post a 'Status' update 6) Select 'Comment' on the status 7) Write a comment Actual: Profie picture are not aligned in comments Expected: Profile pictures to be aligned with the icons Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20140106004001 Gaia: 35a60b82f8cf2d759939a350e2dadbb9d8b2f5dc Gecko: a43cb4b322d3 Version: 28.0a2 Firmware Version: V1.2_20131115
Reporter | ||
Comment 1•11 years ago
|
||
Issue occurs on 1.2 and 1.1 Buri builds. Environmental Variables: Device: Buri 1.2 COM BuildID: 20140106004001 Gaia: 8441587c3b352e052fee07665c21fd192540f19f Gecko: d552c08a72d0 Version: 26.0 RIL Version: 01.02.00.019.102 Firmware Version: V1.2_20131115 Environmental Variables: Device: Buri 1.1 COM BuildID: 20140107041207 Gaia: 6ff3a607f873320d00cb036fa76117f6fadd010f Gecko: 66c4a3131c39 Version: 18.0 RIL Version: 01.01.00.019.281 Firmware Version: V1.2_20131115
Updated•11 years ago
|
Blocks: b2g-facebook
Updated•11 years ago
|
Assignee: nobody → colby
Severity: normal → minor
Status: NEW → ASSIGNED
Priority: -- → P3
Comment 3•11 years ago
|
||
Unable to reproduce on Inari v1.1 and Buri 1.3. Changing status to Resolved - Works for me. If issue occurs again, please re-open.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Updated•6 years ago
|
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•