Description: If the user presses the Home button just after ending a call, the green call information bar's text becomes truncated and is cut off at the bottom. Repro Steps: 1) Updated Buri to Build ID: 20140117004005 2) Begin a call. 3) End the call and immediately press Home. 4) Observe the green bar at the top of the screen. Actual: The text within the green bar is truncated and chopped off at the bottom. Expected: The text within the green bar is not truncated and clearly visible. Environmental Variables Device: Buri 1.3 Mozilla Build ID: 20140117004005 Gecko: http://hg.mozilla.org/releases/mozilla-aurora/rev/2c033140eff4 Gaia: a81ccdc53e45a6adeaae423e104e91bcc1e12b0e Platform Version: 28.0a2 Firmware Version: V1.2-device.cfg Notes: Repro frequency: 100% See attached: bar1.png, bar2.png
This issue seems to be a recurrence of a bug that was fixed in Buri 1.2 Link to bug: https://bugzilla.mozilla.org/show_bug.cgi?id=928025 Checked and does not reproduce in the latest Buri 1.2 Environmental Variables Device: Buri 1.2 Com Ril Build ID: 20140114004002 Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/42a1c35fc831 Gaia: 539a25e1887b902b8b25038c547048e691bd97f6 Platform Version: 26.0 RIL Version: 01.01.00.019.281
Keywords: regression, regressionwindow-wanted
status-b2g-v1.2: --- → unaffected
status-b2g-v1.3: --- → affected
Created attachment 8361990 [details] 2014-01-17-19-10-48.png This issue repros on the first stable 1.3 Buri build (9/19/2013), but instead of showing a large phone number cut off as in Harvey's attached images it can show various other information which is also cut off and briefly stuck in the home page header. I do see the text cut off, but was unable to get a screenshot of it happening. :( .:First Broken Build:. Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20130919040201 Gaia: 0dedb5b3789afc638a0c7c67652937fcb30e77d2 Gecko: 803189f35921 Version: 27.0a1 Firmware Version: v1.2-device.cfg .:Last Working Build:. (probably any latest 1.2 build) Environmental Variables Device: Buri 1.2 Com Ril Build ID: 20140114004002 Gecko: http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/42a1c35fc831 Gaia: 539a25e1887b902b8b25038c547048e691bd97f6 Platform Version: 26.0 RIL Version: 01.01.00.019.281
The STR feels unrealistic here. Can we get STR that reflects a more realistic use case? For example, can you reproduce this just by hitting the home button to go to the homescreen during a call?
(In reply to Jason Smith [:jsmith] from comment #5) > The STR feels unrealistic here. Can we get STR that reflects a more > realistic use case? For example, can you reproduce this just by hitting the > home button to go to the homescreen during a call? I tried for about 70min a bunch of different ways and states of pressing the home button while in a call and I can't get a more simple STR sadly. The only way I can trigger this issue is by ending the call. Is there another way to trigger something similar to ending the call itself?
Ending the call when? Is there timing associated on when the call is ended? I'm looking for more information in regards to step 's timing: 3) End the call and immediately press Home. Specifically between the timeframe when the call is ended & home is hit.
Ending the call during any state (while just in an app or at the home screen) seems to trigger the issue and the timing is relevant as the home button should be pressed while the call UI is transitioning upward from ending the call. If the home button is pressed after the call UI disappears then the window of repro has passed.
Given the high amount of timing required & the fact that the impact isn't terrible, I don't think I'd block on this bug.
The Callscreen has been redesigned and this is no longer valid.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.