Closed
Bug 984127
Opened 10 years ago
Closed 10 years ago
[Sora][Browser]there is a black area when you re-enter the browser by "I'm thinking of ……"
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect, P1)
Firefox OS Graveyard
Gaia::System::Window Mgmt
Tracking
(blocking-b2g:1.3+, b2g-v1.3 verified, b2g-v1.3T verified, b2g-v1.4 unaffected, b2g-v2.0 unaffected)
VERIFIED
FIXED
blocking-b2g | 1.3+ |
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | verified |
b2g-v1.3T | --- | verified |
b2g-v1.4 | --- | unaffected |
b2g-v2.0 | --- | unaffected |
People
(Reporter: sync-1, Assigned: alive)
References
()
Details
Attachments
(3 files)
Mozilla BuildID 20140226004002 Created an attachment (id=663699) VEDIO DEFECT DESCRIPTION: when I re-enter the browser by an input screen,the lower half of the browser interface is black REPRODUCING PROCEDURES: 1.lanuch "WWW.sina.com.cn" 2.press home key to desktop 3.go into "I'm thinking of……",search “Browser” 4.click browser in searching result 5.look at the interface,the lower half of the screen is black ---->KO note: phenomenon of Beetle lite FF and soul3.5 FF is NOT the same,there is no black interface in beetle lite FF EXPECTED BEHAVIOUR: there is no black interface after clicking the browser in searching result ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: 100% For FT PR, Please list reference mobile's behavior:
Comment 2•10 years ago
|
||
Can someone confirm this on the Moz side on 1.3?
Keywords: qawanted,
regression
I think it's blocking issue with high reproduce rate and I found a way to reproduce it easily: 1. on e.me page, search any app that with input field like message/contact/email/browser/calendar/music. 2. enter the app by tap app icon from search result. 3. open a page in the app with input field and tap on it to call up keyboard. 4. press home key back to e.me. 5. tap on search bar on e.me page to call up keyboard. 6. enter the app again by tap app icon from search result. 7. will find black screen at the area of keyboard.
blocking-b2g: --- → 1.3?
Updated•10 years ago
|
QA Contact: pbylenga
Comment 4•10 years ago
|
||
On the latest Buri v1.3 I am able to reproduce the issue using the STRs in Comment 0. However, I am unable to reproduce the issue using the STRs in Comment 3. Returning to the Message app does not reproduce the black area issue, keyboard is disabled and layout is as expected. v1.3 Environmental Variables: Device: Buri v1.3 MOZ BuildID: 20140317004001 Gaia: 0ab8a9cbcef5f23cec904a3d7f7675e44de29951 Gecko: f824e9d91a2d Version: 28.0 Firmware Version: v1.2-device.cfg
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Comment 5•10 years ago
|
||
The Regression Window is 1-20-2014 to 1-21-2014 which falls outside of the date range for available Tinderbox and Inbound builds. The gecko/gaia swap test reveals this is a Gaia issue. Also this issue occurs both with and without APZ enabled. Last Working B2G-RIL build: v1.3 Environmental Variables: Device: Buri v1.3 MOZ BuildID: 20140120004002 Gaia: 63cc8ffd6f2acdce14eb8285e8822ebe62fcab41 Gecko: 37ec3c7fb511 Version: 28.0a2 Firmware Version: v1.2-device.cfg First Broken B2G-RIL build: v1.3 Environmental Variables: Device: Buri v1.3 MOZ BuildID: 20140121004137 Gaia: 47049555282a9a01fb60d1e1421b57e2810c96f5 Gecko: 6f7dfe36ab6c Version: 28.0a2 Firmware Version: v1.2-device.cfg Last Working Gaia / First Broken Gecko: Issue Does NOT reproduce Gaia: 63cc8ffd6f2acdce14eb8285e8822ebe62fcab41 Gecko: 6f7dfe36ab6c Last Working Gecko / First Broken Gaia: Issue DOES reproduce Gaia: 47049555282a9a01fb60d1e1421b57e2810c96f5 Gecko: 37ec3c7fb511 Pushlog: https://github.com/mozilla-b2g/gaia/compare/63cc8ffd6f2acdce14eb8285e8822ebe62fcab41...47049555282a9a01fb60d1e1421b57e2810c96f5
Keywords: regressionwindow-wanted
Updated•10 years ago
|
Component: Gaia::Keyboard → Gaia::System::Window Mgmt
Comment 7•10 years ago
|
||
Please help with fix for the same. Made 1.3+
blocking-b2g: 1.3? → 1.3+
Flags: needinfo?(alive)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → alive
Flags: needinfo?(alive)
Assignee | ||
Comment 9•10 years ago
|
||
Let's do the same thing as v1.4 app_window_manager does.
Attachment #8393301 -
Flags: review?(timdream)
Comment 10•10 years ago
|
||
Comment on attachment 8393301 [details] [review] https://github.com/mozilla-b2g/gaia/pull/17307 Please make sure calling |KeyboardManager.hideKeyboardImmediately();| without a showing keyboard does not result any bad side effect.
Attachment #8393301 -
Flags: review?(timdream) → review+
Assignee | ||
Comment 11•10 years ago
|
||
Comment on attachment 8393301 [details] [review] https://github.com/mozilla-b2g/gaia/pull/17307 Low risk patch to hide keyboard on app launching. NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] [Bug caused by] (feature/regressing bug #): [User impact] if declined: [Testing completed]: [Risk to taking this patch] (and alternatives if risky): [String changes made]:
Attachment #8393301 -
Flags: approval-gaia-v1.3?
Comment 12•10 years ago
|
||
(In reply to Alive Kuo [:alive][NEEDINFO!][:艾莉芙] from comment #11) > Comment on attachment 8393301 [details] [review] > https://github.com/mozilla-b2g/gaia/pull/17307 > > Low risk patch to hide keyboard on app launching. > > NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to > better understand the B2G approval process and landings. > > [Approval Request Comment] > [Bug caused by] (feature/regressing bug #): > [User impact] if declined: > [Testing completed]: > [Risk to taking this patch] (and alternatives if risky): > [String changes made]: :alive, can you please help with more details request in the above comment ?
Updated•10 years ago
|
Flags: needinfo?(alive)
Assignee | ||
Comment 13•10 years ago
|
||
(In reply to bhavana bajaj [:bajaj] from comment #12) > (In reply to Alive Kuo [:alive][NEEDINFO!][:艾莉芙] from comment #11) > > Comment on attachment 8393301 [details] [review] > > https://github.com/mozilla-b2g/gaia/pull/17307 > > > > Low risk patch to hide keyboard on app launching. > > > > NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to > > better understand the B2G approval process and landings. > > > > [Approval Request Comment] > > [Bug caused by] (feature/regressing bug #): > > [User impact] if declined: > > [Testing completed]: > > [Risk to taking this patch] (and alternatives if risky): > > [String changes made]: > > :alive, can you please help with more details request in the above comment ? I don't know how to say but only technical detail. The issue is that the browser app is resized by the keyboard once, and if the user is launching the ever-resized app on keyboard is shown we will resize again which is wrong. The solution is there in v1.4 from bug 907013, we will hide the keyboard on each app launching request. And since v1.4/v1.5 doesn't have this issue and no other regressions had been found I think it's safe to introduce the same thing to v1.3 and the modification is little.
Flags: needinfo?(alive)
Comment 14•10 years ago
|
||
Comment on attachment 8393301 [details] [review] https://github.com/mozilla-b2g/gaia/pull/17307 Thanks for the comments alive. Lets get this landed and a parallel verification on 1.3 by QA/Reporter
Attachment #8393301 -
Flags: approval-gaia-v1.3? → approval-gaia-v1.3+
Comment 15•10 years ago
|
||
(In reply to Jack Liu from comment #3) > I think it's blocking issue with high reproduce rate and I found a way to > reproduce it easily: > > 1. on e.me page, search any app that with input field like > message/contact/email/browser/calendar/music. > 2. enter the app by tap app icon from search result. > 3. open a page in the app with input field and tap on it to call up keyboard. > 4. press home key back to e.me. > 5. tap on search bar on e.me page to call up keyboard. > 6. enter the app again by tap app icon from search result. > 7. will find black screen at the area of keyboard. HI Jack, Can you please confirm this is fixed in the latest build once this lands ?
Assignee | ||
Comment 16•10 years ago
|
||
v1.3 landed. https://github.com/mozilla-b2g/gaia/commit/f1c58f9f3b5d538afdd71ad3c22106200bc7ece5
Status: NEW → RESOLVED
Closed: 10 years ago
status-b2g-v1.3:
--- → fixed
status-b2g-v1.4:
--- → unaffected
status-b2g-v2.0:
--- → unaffected
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v1.3T:
--- → fixed
Comment 17•10 years ago
|
||
Verified as fixed on the latest v1.3 Buri build. 3/25 Environmental Variables: Device: Buri 1.3 MOZ RIL BuildID: 20140325004002 Gaia: b789780c53adaac199787f51615375f721edfef4 Gecko: 37917eb0dfeb Version: 28.0 Firmware Version: V1.2-device.cfg
Keywords: verifyme
Comment 18•10 years ago
|
||
Leaving verifyme keyword because this issue still needs to be checked on the v1.3T branch.
Updated•10 years ago
|
Flags: in-moztrap?
Updated•10 years ago
|
Flags: in-moztrap? → in-moztrap+
Comment 19•10 years ago
|
||
Verified on the latest Tarako build 1.3T Environmental Variables: Device: Tarako 1.3T BuildID: 20140530014002 Gaia: e68858693b71d917c9c5ee7e215f7ceea04635f7 Gecko: 1945abae19ff Version: 28.1 Firmware Version: SP6821a-Gonk-4.0-4-29 1.3 tarako: no black interface on the lower half of sina.com
Comment 20•9 years ago
|
||
According to comment #18 and comment #19, Clear Verifyme keyword.
Keywords: regression,
verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•