Closed Bug 1101780 Opened 10 years ago Closed 6 years ago

[Marketplace] Holding back button and selecting "open link in new tab" takes user to a blank page.

Categories

(Firefox OS Graveyard :: General, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: jthomas, Unassigned)

References

()

Details

(Whiteboard: [2.1-exploratory-3][systemsfe])

Attachments

(1 file)

Description:
After the user selects an app to view in the Marketplace there is an option to hit the back button. If the back button is pressed and held there will be the option to view the link on another page. If this option is selected the user will be taken to a blank page with a small "x" to the top left of the page. 


Repro Steps:
1) Update a Flame device to BuildID: 20141119001205
2) Launch Marketplace app.
3) Select any app for additional info.
4) Press and hold back button.
5) Open link in new tab.
  
Actual:
User is taken to a blank page with a small "x" at the top left.
  
Expected: 
It is expected that the user will be able to open a link in a new tab, or that this option would be disabled.
  
Flame 2.1 

Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash)
Build ID: 20141119001205
Gaia: 1b231b87aad384842dfc79614b2a9ca68a4b4ff3
Gecko: 95fbd7635152
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
  
Repro frequency: 100%
See attached: Logcat & Video
Video: http://youtu.be/0Wx9ef87yxY
This issue does NOT occur on Flame 2.2 KK (319mb) and Flame 2.0 KK (319mb)

Flame 2.2
Result: Open link in new tab works successfully.

Device: Flame 2.2 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141119040205
Gaia: e64428c5b2dce5db90b75a5055077a04f4bd4819
Gecko: bc2c36dda0a9
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
-----------------------------------------------

Flame 2.0
Result: Press and holding is disabled in the 2.0

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
Build ID: 20141119000207
Gaia: 1ede2666f1e6c1b3fd3b282011caf0cbc59544b0
Gecko: faa64077b0c2
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: [2.1-exploratory-3] → [2.1-exploratory-3][systemsfe]
[Blocking Requested - why for this release]:

This issue does not occur on Master. The pages look as expected so nominating this 2.1?
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Not a common use case and low user impact.
blocking-b2g: 2.1? → backlog
I thought this bug was already filed but I can't find the dupe.  Moving to Firefox OS product as I don't think this is a Marketplace setting (and also that it only occurs on 2.1).  If Marketplace is able to disable this option please let us know how.
Component: Consumer Pages → General
Product: Marketplace → Firefox OS
Version: Avenir → unspecified
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 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: