Closed Bug 934648 Opened 11 years ago Closed 11 years ago

[B2G][Browser] Returning to in-browser view from fullscreen on youtube videos reveals half of the homescreen.

Categories

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

Product:
Firefox OS Graveyard
Component:
Gaia::System::Window Mgmt
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: laliaga, Unassigned)

Details

(Keywords: regression)

Attachments

(3 files)

2013-11-04-13-01-58.png
255.89 KB, image/png
Details
Logcat and dmesg.zip
10.58 KB, application/zip
Details
2013-12-09-14-37-46.png
107.90 KB, image/png
Details
Attached image 2013-11-04-13-01-58.png —
When visiting youtube.com, if the user makes a video fullscreen then returns to in-browser view, the homescreen becomes visible and cuts off half the browser. Repro Steps: 1. Update Buri 1.3 device to buildID: 20131104044747. 2. Access www.youtube.com > play any video > tap fullscreen. 3. Return to in-browser from fullscreen view. Actual Results: Browser becomes cutoff and the homescreen is displayed. Expected Results: Browser remains fully rendered at all times. Repro Rate: 3/6 50% Gaia 1aee772a384f1ed1148f08c6c7df45d2fe35506e SourceStamp b4143e04bea1 BuildID 20131104044747 Version 28.0a1 Attached: Screenshot
I'm doubtful this is a browser bug - probably more likely a system bug.
blocking-b2g: --- → 1.3?
Component: Gaia::Browser → Gaia::System::Window Mgmt
Keywords: regression, regressionwindow-wanted
Lucas, can you supply two things please? The adb shell logcat as well as the adb shell dmesg? I wonder if this has to do with bug 905882/bug 923303?
Flags: needinfo?(laliaga)
Attached file Logcat and dmesg.zip —
Logcat and dmesg attached.
Flags: needinfo?(laliaga)
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #2) > Lucas, can you supply two things please? The adb shell logcat as well as > the adb shell dmesg? > > I wonder if this has to do with bug 905882/bug 923303? I'm doubtful this is related to those two bugs. This is likely a regression from the window management refactoring work going on.
QA Contact: nkot
Regression range: -last working- Buri BuildID: 20131028040200 Gaia: 31c260b5c853fe78d6bf44c6aeec52a651c3f025 Gecko: 59ff3a2a708a Version: 27.0a1 Firmware: 20131015 -first broken- Buri BuildID: 20131029040205 Gaia: 92c097fd7ac9886f937d9decb0e03ab673deaa1b Gecko: 518f5bff0ae4 Version: 28.0a1 Firmware: 20131015
Keywords: regressionwindow-wanted
The similar issue is noticed on the latest build with different steps. 1) Open "Browser" app from the home screen 2) Rotate the device to landscape mode 3) Press the "Home" button in the landscape mode to return to the home screen 4) Rotate the device to portrait view and open the "Browser" Actual result: The Browser reveals only half screen Expected result: The browser opens in the full page view Device: Buri 1.3 Central build BuildID: 20131111040200 Gaia: bcb4f94524ef02e9ef16b604d16c39e5a9c41281 Gecko: bc8c1eb0f2ba Version: 28.0a1 Firmware Version: US_20131104
Gaia: 67866e82379e751646aa5f0fd6a7a4268e9529c1 Gecko: http://hg.mozilla.org/mozilla-central/rev/597287004ff5 BuildID 20131120062258 Version 28.0a1 OEM Build : v1.2_20131115 Buri 1. go to youtube 2. play a video 3. go to landscape 4. go to portrait. This will cause the bug as well.
I was able to reproduce this issue when APZ was turned on for the Video app. It's an APZ issue.
Depends on: 916185
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #8) > I was able to reproduce this issue when APZ was turned on for the Video app. > It's an APZ issue. I don't think this is related to the meta viewport work going on in that bug.
(In reply to Jason Smith [:jsmith] from comment #9) > (In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from > comment #8) > > I was able to reproduce this issue when APZ was turned on for the Video app. > > It's an APZ issue. > > I don't think this is related to the meta viewport work going on in that bug. This reproduces without the APZ pieces turned on.
Removing the dependency here because this was filed in the browser app content, which is not related to the work going on for turning on APZC across Gaia.
No longer depends on: 916185
I agree that it does not have to do with : bug 905882/bug 923303. I should have stated that APZ makes it easier to see. I still think it does have to do with not having a meta viewport: https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag see first image. Things will get cut off/mishappen in the content size without meta viewports.
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #12) > I agree that it does not have to do with : bug 905882/bug 923303. > I should have stated that APZ makes it easier to see. > > I still think it does have to do with not having a meta viewport: > https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag > see first image. Things will get cut off/mishappen in the content size > without meta viewports. I don't think so - the screenshot involves bleeding across different apps, which usually is a bug involving window management in Gaia.
QA Wanted - Is this still reproducible? There was a patch that landed recently that should have fixed this.
Keywords: qawanted
Attached image 2013-12-09-14-37-46.png —
No issue occurs when using comment 0 repro, but a new issue occurs when trying comment 7 and can be seen in the attached image. Should a new bug be written as the issue that started this bug is no longer seen. Environmental Variables: Device: Buri 1.3 mozRIL BuildID: 20131209053402 Gaia: 1d45d1dc3201059d5c8f2efdeb92c04576d8e161 Gecko: 9f12a9fab080 Version: 28.0a1 RIL Version: 01.02.00.019.102 Firmware Version: 20131115
Keywords: qawanted
status-firefox29: --- → affected
status-firefox29: affected → ---
(In reply to gbennett from comment #16) > Created attachment 8344928 [details] > 2013-12-09-14-37-46.png > > No issue occurs when using comment 0 repro, but a new issue occurs when > trying comment 7 and can be seen in the attached image. Should a new bug be > written as the issue that started this bug is no longer seen. > > Environmental Variables: > Device: Buri 1.3 mozRIL > BuildID: 20131209053402 > Gaia: 1d45d1dc3201059d5c8f2efdeb92c04576d8e161 > Gecko: 9f12a9fab080 > Version: 28.0a1 > RIL Version: 01.02.00.019.102 > Firmware Version: 20131115 I'd file a new bug for that issue. Can you file it?
Status: NEW → RESOLVED
blocking-b2g: 1.3? → ---
Closed: 11 years ago
Flags: needinfo?(gbennett)
Resolution: --- → WORKSFORME
(In reply to Jason Smith [:jsmith] from comment #17) > I'd file a new bug for that issue. Can you file it? Sweet, and I can. Would you like the new bug linked here as well?
Flags: needinfo?(gbennett)
(In reply to gbennett from comment #18) > (In reply to Jason Smith [:jsmith] from comment #17) > > > I'd file a new bug for that issue. Can you file it? > > Sweet, and I can. Would you like the new bug linked here as well? Sure.
Comment 0 STR now repros bug 948199.
Meant to say comment 7 in above statement.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: