Closed Bug 1231237 Opened 4 years ago Closed 2 years ago

Pin Page overlay is briefly still functional after it is dismissed.

Categories

(Firefox OS Graveyard :: Gaia::Browser, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(b2g-v2.5 affected, b2g-master affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.5 --- affected
b2g-master --- affected

People

(Reporter: Marty, Unassigned)

References

()

Details

(Keywords: polish, Whiteboard: [2.6-Daily-Testing][Spark][Systemsfe])

Attachments

(1 file)

Attached file logcat_pin-dismiss.txt
Description:
As the Pin Page overlay is dismissing, the user is still able to select options as it fades out. This could lead to people accidentally pinning pages or sites after dismissing the overlay.

Note: The user is also able to pin as both a site and a page by tapping both quickly.

Repro Steps:
1) Update a Aries to 20151208121557
2) Open the browser app and navigate to a web page (www.google.com)
3) Pin the Page to the homescreen by selecting the Ellipsis (...) > Pin > Pin Page
4) Press the X to dismiss the overlay, then immediately press where the 'Pin Page' button was

Actual:
The Page is stilled Pinned, despite the overlay being dismissed.

Expected:
The Page cannot be pinned after dismissing the overlay.

Environmental Variables:
Device: Aries 2.6
Build ID: 20151208121557
Gaia: 6b430ea7274af4c352de16b75e6bb85d7621ca83
Gecko: 2bdd9ec79799eff3ceec0a318f5a0632d918a527
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 45.0a1 (2.6)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0

Repro frequency:  10/10
See attached: Video (URL), Logcat
This issue DOES occur on the latest Flame 2.6 and 2.5 Nightly builds.
The Page is stilled Pinned, despite the overlay being dismissed.
Note: The window behavior is different on 2.5, so the issue doesn't seem as severe.

Environmental Variables:
Device: FlameKK 2.6 (512MB)
BuildID: 20151208030225
Gaia: 6b430ea7274af4c352de16b75e6bb85d7621ca83
Gecko: 2bdd9ec79799eff3ceec0a318f5a0632d918a527
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 45.0a1 (2.6) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0

Environmental Variables:
Device: FlameKK 2.5 (512MB)
BuildID: 20151208120554
Gaia: 2d54c29f429bed790b5d8284633812dc2b782518
Gecko: ff31a251b2f6149edf4fc0a199133ef2e190ceac
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 44.0a2 (2.5) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Edge case but could lead to bad user experience so nominating to block.  Can I get your opinion as well though Alison?
blocking-b2g: --- → 2.6?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado) → needinfo?(ashiue)
hmm, I do not think this issue is severe enough to be a blocker since this is not a common use case.

Hi Gregor,
Could you please dispatch this issue to suitable person to help to check? Thank you.
Flags: needinfo?(ashiue) → needinfo?(anygregor)
Whiteboard: [2.6-Daily-Testing][Spark] → [2.6-Daily-Testing][Spark][Systemsfe]
Lets fix it but we won't block a release on this issue.
blocking-b2g: 2.6? → ---
Flags: needinfo?(anygregor)
Keywords: polish
Priority: -- → P1
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][COM=Pin the Web]
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.