Closed
Bug 705678
Opened 12 years ago
Closed 12 years ago
[ICS] - AwesomeBar truncated in landscape view
Categories
(Firefox for Android Graveyard :: General, defect, P1)
Tracking
(firefox11 fixed, fennec11+)
VERIFIED
FIXED
People
(Reporter: aaronmt, Assigned: sriram)
References
Details
(Whiteboard: [ICS])
Attachments
(1 file)
56.27 KB,
image/png
|
Details |
See attached screenshot. -- Samsung Nexus S (Android 4.0.1) 20111128040211 http://hg.mozilla.org/projects/birch/rev/aa6ad7ab9b43
Assignee | ||
Comment 1•12 years ago
|
||
While investigating this bug, I found that, we are using 54dip for browser url bar, and in ICS, the action bar is smaller than this. On fixing it to take the actionBarSize (provided by honeycomb+), I found that, in ICS, the size differs between landscape and portrait modes. On a screenshot, I got 96px in portrait mode and 80px on landscape mode (hardware pixels). http://cl.ly/3v21150g1l3N2F1j2d0d and http://cl.ly/0E3z0Z0A093E3G0g1T3n Also, the activity is not re-created on rotation. So, actionBarSize (even if ICS provides it to be 80px on portrait), won't be taken to redraw this portion. This get even scary, with more shrinking on rotation. http://cl.ly/193Z0C3s1i11020a0Q15 I would like to try to check if layout-landscape-v11/ and layout-portrait-v11/ folders can help us. But still, I'm worried about "tabs-add" button being square. We also need specs for these two different sizes.
Updated•12 years ago
|
Assignee: nobody → sriram
Priority: -- → P1
Comment 2•12 years ago
|
||
It's not just in landscape mode. It's clipped worse in landscape mode but it's also clipped in portrait by at least a couple of pixels.
Comment 3•12 years ago
|
||
Should be fixed by bug 705481 and bug 708700
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•12 years ago
|
Status: RESOLVED → VERIFIED
Updated•12 years ago
|
tracking-fennec: --- → 11+
Updated•12 years ago
|
status-firefox11:
--- → fixed
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•