Closed Bug 1021426 Opened 10 years ago Closed 10 years ago

Facebook external link makes ghost window (may happen in other apps but not tested yet)

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.0+)

RESOLVED DUPLICATE of bug 1021658
blocking-b2g 2.0+

People

(Reporter: Omega, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [2.0-FL-bug-bash][systemsfe])

Attachments

(1 file)

Attached image 2014-06-05-20-06-55.png (deleted) —
Device: Flame Gaia: 2014-06-05 23:34:17 BuildID: 20140602160205 Version: 2.0.0.0-prerelease Steps to Reproduce 1) Install Facebook app and sign in 2) Tap any post linking to external website 3) Long press home button to show task manager Expected Results There is a ghost window which cannot be removed Actual Results There is no ghost window
Sorry for typo, it should be: Actual Results There is a ghost window which cannot be removed Expected Results There is no ghost window
QA Wanted to see if this issue is reproducible on 1.4.
Keywords: qawanted
This issue does NOT occur on Flame 1.4: Environmental Variables: Device: Flame 1.4 Build ID: 20140610000204 Gaia: 57c6a24f7c7d16aac132f3cecd3ff9ee8d53cf78 Gecko: 54a7aa1a0423 Version: 30.0 (1.4) Firmware Version: v10G-2
Keywords: qawanted
QA Contact: ychung
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
QA Whiteboard: QAnalyst-Triage+
QA Whiteboard: QAnalyst-Triage+ → [QAnalyst-Triage+]
Joshua - The triage marking here looks incorrect. The tester here did not mark the bug with the regression & regressionwindow-wanted keyword. If the bug reproduces on 2.0, but doesn't reproduce on 1.4, then it's a regression.
Flags: needinfo?(jmitchell)
Right you are, sorry about that - still working out the new process.
Flags: needinfo?(jmitchell)
blocking-b2g: --- → 2.0?
Whiteboard: [2.0-FL-bug-bash] → [2.0-FL-bug-bash][systemsfe]
QA Contact: ychung → jmercado
QA-Wanted work not completed yet - switching QA Triage Flag
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
B2g-inbound Regression window Last working Environmental Variables: Device: Flame BuildID: 20140519053002 Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348 Gecko: 8508ab79921f Version: 32.0a1 First Broken Environmental Variables: Device: Flame BuildID: 20140519143007 Gaia: 83f622db256dad92e8c97cccf9c71611d0e5a737 Gecko: 0317c5d3befc Version: 32.0a1 Last working gaia / First broken gecko - Issue does NOT occur Gaia: 8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348 Gecko: 0317c5d3befc First broken gaia / Last working gecko - Issue DOES occur Gaia: 83f622db256dad92e8c97cccf9c71611d0e5a737 Gecko: 8508ab79921f Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/8a2352d5b7be27ec4b1ea18c680ebcd0b6d34348...83f622db256dad92e8c97cccf9c71611d0e5a737
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
It seems that bug 935260 is the origin of the problem. Can you have a look Sam?
Blocks: task-manager
Flags: needinfo?(sfoster)
Alive, I'm happy to look into this but wanted your insight first as I think I've seen you handling similar bugs recently. Are these symptoms familiar? I can't rule out the CardsView refactor as the cause but it seems unlikely...
Flags: needinfo?(sfoster) → needinfo?(alive)
blocking-b2g: 2.0? → 2.0+
I guess if we uplift https://bugzilla.mozilla.org/show_bug.cgi?id=1021658 we could avoid this.
Flags: needinfo?(alive)
I just think 1021658 fixes this issue.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: