Closed Bug 971095 Opened 10 years ago Closed 3 years ago

Content shrinks and does not take entire screen width after browser reset

Categories

(Firefox for Android Graveyard :: Toolbar, defect)

30 Branch
ARM
Android
defect
Not set
normal

Tracking

(firefox27 affected, firefox28 affected, firefox29 affected, firefox30 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox27 --- affected
firefox28 --- affected
firefox29 --- affected
firefox30 --- affected

People

(Reporter: ioana.chiorean, Unassigned)

Details

Build: Beta 28.0b2
Nexus 4 - android 4.4

Steps:
1. Perform a search with yahoo
2. Change system's language
3. Go to fennec

Actual Results:
- the page is displayed only on the half left side

Expected results:
- the page should be displayed on all the apps page's area

Note: 
- see http://www.youtube.com/watch?v=2FgnX2WmJro
- reproduced on Beta with several languages
- on nightly/aurora at the 3rd change
- a reload of the page will fix it
Component: General → Graphics, Panning and Zooming
Summary: Wrong display after L10n change → Content shrinks and does not take entire screen width after browser reset
Is 27 affected?
Flags: needinfo?(ioana.chiorean)
Yes, 
I am able to reproduce it on Release 27 too (at the 3rd change of l10n)
Flags: needinfo?(ioana.chiorean)
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.