Add to Home Screen opens a new tab with the page

NEW
Unassigned

Status

()

Firefox for Android
Awesomescreen
P3
normal
a year ago
4 months ago

People

(Reporter: BogdanS, Unassigned)

Tracking

Trunk
ARM
Android
Points:
---

Firefox Tracking Flags

(fennec+, firefox56 affected, firefox57 affected, firefox58 affected)

Details

(Reporter)

Description

a year ago
Device:  
 - Huawei Honor 8 (Android 6.0);
 - Motorola Nexus 6 (Android 7.0);
 - Huawei Honor 5X (Android 5.1.1);

Scenario 1 STR:
1. Open any webpage;
2. Open the Menu go to Page and select the Add to Home Screen option;
3. Minimize the app and select the shortcut created on the Home Screen.

Scenario 2 STR:
1. Open any webpage;
2. Open the Menu go to Page and select the Add to Home Screen option;
3. Close the app and select the shortcut created on the Home Screen.

Expected result:
 The tab with the webpage should be opened instead of opening a new tab.

Actual result:
Scenatio 1 - A new tab is opened regardless of the fact that the page is already open in another tab, if the user minimizes the app and selects the shortcut for a second time he is sent to the proper tab;
Scenario 2 - A new tab is opened every time the user closes the app and reopens it from the shortcut.

Notes:
 This issue is reproducible no matter how the user creates a home screen shortcut. (Top Sites, Bookmarks or History context menu)
Too late for firefox 52, mass-wontfix.
status-firefox52: affected → wontfix
(Reporter)

Updated

7 months ago
tracking-fennec: --- → ?
status-firefox57: --- → affected
status-firefox58: --- → affected

Comment 2

7 months ago
Hi Bogdan
Is this still happening?
Flags: needinfo?(bogdan.surd)
Priority: -- → P2

Comment 3

7 months ago
Just tested and it's still happening.
Please help prioritize this. We should "switch to tab" instead of "open a new tab" is the same url presented.
tracking-fennec: ? → +
Flags: needinfo?(wehuang)
Flags: needinfo?(jcheng)
(Reporter)

Comment 4

7 months ago
Hi Nevin,

Tested on the Nexus 6 device and yes this is still happening.
status-firefox51: affected → ---
status-firefox52: wontfix → ---
status-firefox53: affected → ---
status-firefox54: affected → ---
status-firefox56: --- → affected
Flags: needinfo?(bogdan.surd)

Comment 5

7 months ago
Tried and seems some inconsistency here, but I wonder if we expect the behavior is the same for both scenarios? (for example sometimes the tab with the page could be closed by user before closing the app, so we can only open a new tab for it) Is it the case before? (also ni UX Jack for comment).

P2 +1.
Flags: needinfo?(wehuang) → needinfo?(jalin)

Comment 6

7 months ago
Agree with consistency.
For both scenarios, I suggest we do the same behavior that is "Press the shortcut created on the Home Screen, then direct to the existed tab with the webpage. If there is no the existed tab with the webpage, open it in a new tab".
Flags: needinfo?(jalin)
(Reporter)

Updated

6 months ago
Duplicate of this bug: 1417650

Comment 8

6 months ago
Part of this (when Firefox isn't already running) is bug 1249318. Other than that I didn't notice anything strange while working on bug 1407188 and bug 1417650 is a recent regression.
[triage] Non-critical.
Flags: needinfo?(jcheng)
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.