Closed Bug 1169774 Opened 10 years ago Closed 7 years ago

[Window Mgmt] Returning to an app with open Dialog window will display the app first then push Dialog to foreground

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(feature-b2g:3.0?, tracking-b2g:+, b2g-v2.1 unaffected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
feature-b2g 3.0?
tracking-b2g +
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: onelson, Unassigned)

References

()

Details

(Whiteboard: [3.0-Daily-Testing], [Spark] polish)

Attachments

(1 file)

Attached file logcat_20150529_1247.txt (deleted) —
Description: When a user is an application and opens a Dialog window, they can observe odd UI behavior if they transition between homescreen and the app. Tapping home to return to homescreen, then reopening the app will have the user observe the app open then the dialog taking the UI foreground. The transition seems unnecessary as the UI for the Dialog was present on the screen when the user navigated away and is expected to be there when they return. * Issue responds faster on higher memory devices Repro Steps: 1) Update a Flame to 20150529010201 2) Open Settings app 3) Navigate to 'Messaging Settings' 4) Tap 'Auto Retrieve' dialog to open 5) Tap home button with dialog open 6) Open Settings app 7) Observe UI Actual: App opens then dialog opens after a second Expected: * App opens with dialog open -- or -- * App opens, no dialog [2.1 behavior] Environmental Variables: ------------------------------- Device: Xperia Z3 Compact (B2G) BuildID: 20150528210322 Gaia: 18f7c340f970991a10c288310bbfd4d105a1430c Gecko: b7aed25b94251ea192021885323f15e87fc39321 Version: 41.0a1 (3.0) Device: Flame 3.0 Build ID: 20150529010201 Gaia: e7d268074ee3c9eeb191c2205c0e35992fb3915d Gecko: f986e55c4e0b Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Device: Flame 2.2 BuildID: 20150529002502 Gaia: a57ec5786c9f941c690266bbb26049dbb8482b05 Gecko: 6e9875ef5297 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 ********************************** Issue DOES NOT REPRO on 2.1 for flame devices Results: Returning to an app with dialog window open does not open dialog window Device: Flame 2.1 BuildID: 20150529001200 Gaia: 2304a1f6327c2ccf35d6995ee16f2231ed1f22a3 Gecko: 894528758073 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ------------------------------- Repro frequency: 5/5 See attached: video- https://youtu.be/ujADqf6n2YA logcat
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Keywords: regression
I dont see this on my 3.0 build from 4/13
QA Contact: jmercado
What I'm seeing from 4/13 is that it begins to fade after about .4 seconds it fades to the dialogue window instead of snapping to it like it does on builds from today. This still doesn't match the expected results in comment 0 so im going back further.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Bug 1029943 may have caused this issue. Please see the pushlog. B2g-inbound Regression Window Last Working Environmental Variables: Device: Flame 2.2 BuildID: 20140905062812 Gaia: 04bfb7cab6a5485b650dac75cf99b8509ae148fc Gecko: 6aa95efb9322 Version: 35.0a1 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 First Broken Environmental Variables: Device: Flame 2.2 BuildID: 20140905063113 Gaia: 04bfb7cab6a5485b650dac75cf99b8509ae148fc Gecko: 0bb6b880744e Version: 35.0a1 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Last Working gaia / First Broken gecko - Issue DOES occur Gaia: 04bfb7cab6a5485b650dac75cf99b8509ae148fc Gecko: 0bb6b880744e First Broken gaia / Last Working gecko - Issue does NOT occur Gaia: 04bfb7cab6a5485b650dac75cf99b8509ae148fc Gecko: 6aa95efb9322 Gaia Pushlog: http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=6aa95efb9322&tochange=0bb6b880744e
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Ting-Yu Lin, can you take a look at this please? This might have been caused by the work done for bug 1029943.
Blocks: 1029943
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(tlin)
I can still reproduce this issue on master with preferences "selectioncaret.enabled" and "touchcaret.enabled" off, so it's unlikely that bug 1029943 causes this issue. Tim, your changes are also in the pushlog in comment 3. Do you have any idea about this Gaia behavior?
Flags: needinfo?(tlin) → needinfo?(timdream)
Should be caused by my patch, but I don't think without the patch we would get exactly the expected behavior. Anyhow, this should be gone when bug 1162360 is landed.
Assignee: nobody → timdream
Blocks: 1057898
No longer blocks: 1029943
Flags: needinfo?(timdream)
Depends on: 1162360
Please help me test the latest master with bug 1162360 included.
Keywords: qawanted
This issue still occurs in the latest Flame 3.0 build. Actual Results: The dialogue window shows up after being delayed. Environmental Variables: Device: Flame 3.0 BuildID: 20150617010205 Gaia: 6271f932e1e918a35ee89f54288bd13385143a71 Gecko: d7c148c84594 Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 41.0a1 (3.0) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 3 and comment 8 contradicts with each other. Not sure what happen here, but we should try to see what can be improved.
Actually, I don't think this can count as a regression at all based on comment 8. We can't say this is a regression of X when backout of X doesn't fix it... I am going to remove the references and leave this bug as-is and leave it as future possibility for improvement.
Assignee: timdream → nobody
No longer blocks: 1057898
feature-b2g: --- → 3.0?
tracking-b2g: --- → +
No longer depends on: 1162360
Keywords: regression
Whiteboard: [3.0-Daily-Testing], [Spark] → [3.0-Daily-Testing], [Spark] polish
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: