1059864 - [Notification] When rotating the phone to landscape, the notification screen is not lock to portrait

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

Description

[pete siphantong [:Petes]]

Attachment: bn.txt

Description:
When rotating the phone to landscape, the notification screen is not lock to portrait and the layout does not fit the screen 


Repro Steps:
1) Update a Flame device to BuildID: 20140827040203
2) Go to Browser
3) Pull down the notification screen 
4) Rotate the phone


Actual:
the notification screen is not lock to portrait and the layout does not fit the screen 

Expected:
the notification screen is lock to portrait 

Environmental Variables:
Device: Flame Master (319mb)
BuildID: 20140827040203
Gaia: 6e804a42ab90f4251c7fe8c68731dc1c6abd8006
Gecko: 0753f7b93ab7
Version: 34.0a1 (Master) 
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 


Note: layout does not fit the screen only occur on the 2.1


Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/2101/
See attached: screenshot, logcat

Comment 1

[pete siphantong [:Petes]]

Attachment: 2014-08-27-16-40-05.png

Comment 2

[pete siphantong [:Petes]]

This issue also reproduces on the Flame 2.1 (512mb), Open C 2.1, Flame 2.0 (319mb), Open C 2.0, Flame 1.4 (319mb), and the Open C 1.4. The notification screen is not lock to portrait

Flame 2.1

Environmental Variables:
Device: Flame Master (512mb)
BuildID: 20140827040203
Gaia: 6e804a42ab90f4251c7fe8c68731dc1c6abd8006
Gecko: 0753f7b93ab7
Version: 34.0a1 (Master) 
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Open C 2.1

Environmental Variables:
Device: Open_C Master
Build ID: 20140827040203
Gaia: 6e804a42ab90f4251c7fe8c68731dc1c6abd8006
Gecko: 0753f7b93ab7
Version: 34.0a1 (Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.0

Environmental Variables:
Device: Flame 2.0 (319mb)
BuildID: 20140827000204
Gaia: d72f8ad53448aed577c01ff6e11d958463f261e7
Gecko: 2a18149b3ae8
Version: 32.0 (2.0) 
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Open C 2.0

Environmental Variables:
Device: Open_C 2.0
Build ID: 20140827000204
Gaia: d72f8ad53448aed577c01ff6e11d958463f261e7
Gecko: 2a18149b3ae8
Version: 32.0 (2.0)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 1.4

Environmental Variables:
Device: Flame 1.4 (319mb)
BuildID: 20140827003002
Gaia: 05653cb12d324649687dad3eeb2ea373a2ad84d4
Gecko: 7ad0648b8447
Version: 30.0 (1.4)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Open C 1.4

Environmental Variables:
Device: Open_C 1.4
BuildID: 20140827003002
Gaia: 05653cb12d324649687dad3eeb2ea373a2ad84d4
Gecko: 7ad0648b8447
Version: 30.0 (1.4)
Firmware: P821A10v1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Comment 3

[KTucker [:KTucker][Inactive 3/4/2016]]

[Blocking Requested - why for this release]:

Nominating this 2.1? This is a regression as far as the notification bar being cutoff.

Comment 4

[Jason Smith [:jsmith]]

Kevin - I think there's two problems being talked about in this bug - one is talking about the fact that the notification tray is not locked to portrait and the other is involving the fact that notification tray isn't filing the full screen. The notification tray not filing the full screen is a bad regression, but the notification tray not locked to portrait is in fact expected behavior.

As such, we probably should close this bug as invalid & refile a new bug focusing on the fact the notification tray isn't filing the full screen, as that's a bad regression. Can you do that?

Comment 5

[pete siphantong [:Petes]]

wrote up the notification cutoff issue, https://bugzilla.mozilla.org/show_bug.cgi?id=1060118

Comment 6

[KTucker [:KTucker][Inactive 3/4/2016]]

The notification bar should go landscape mode in browser so closing this as invalid. The other issue with the cutoff has been written as stated in comment 5