1486494 - Cannot engage with mobile Facebook marketplace in Firefox Android browser

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect)

Description

[Chris More [:cmore]]

Steps to reproduce:

1) Install Firefox release on an Android phone. (only tested on version 61.0.2).

2) Log in to Facebook.com, which should redirect to m.facebook.com

3) Go to the menu in Facebook and click marketplace

4) Search for any potential for sale item

5) In the listing of items, click any item to view more details and/or contact the seller.

Expected results:

Able to click marketplace result item pictures and/or meta data

Actual results:

Unable to click anything. Touching any part of the marketplace items on the results page does not do anything and you are unable to engage. The only way around is using Chrome mobile or a desktop browser. 

I don't believe this issue existed until the past few months when I noticed it stopped working.

Comment 1

[Jan Henning [:JanH]]

(In reply to Chris More [:cmore] from comment #0)
> I don't believe this issue existed until the past few months when I noticed
> it stopped working.

Does it still work if you try some older Nightly build using mozregression or manually from http://ftp.mozilla.org/pub/mobile/nightly/? I.e. did it break because of a change on our side, or did Facebook change something on their end?

Another thing that might be worth testing - what happens if you install a user agent switcher and pretend to be (mobile) Chrome?

Comment 2

[Mike Taylor [:miketaylr]]

Note that spoofing as Chrome Mobile (which we currently do in Nightly) doesn't make a difference here.

Not a recent regression (at least, this reproduces in Fennec 55).

For the following markup, there are 2 bound event listeners that may be relevant.

<div class="_2rgt _1j-g _2rgt _3n0b" id="u_a_5m" data-nt="NT:BOX_3" data-ntid="u_a_5m">
  <a class="_9_7 _643_" href="/marketplace/item/2062443580454703/?ref=bookmarks"
  onclick="return false;" rel="ignore" style="flex-grow:0;flex-shrink:1;padding:0 3px 0 0"><div class="_y4m _2rgt _1j-f _2rgt _3zi4 _2rgt _1j-f _2rgt"
    id="u_a_5h" data-nt="NT:BOX_3_CHILD" style="flex-grow:1;flex-shrink:1;">
    <div class="_30up" style="padding-bottom: 100%"></div><img src="https://scontent-dfw5-1.xx.fbcdn.net/v/t1.0-0/cp0/e15/q65/c0.35.320.320/p320x320/40087870_1791478327616753_4494770158157430784_n.jpg?_nc_cat=0&amp;efg=eyJpIjoidCJ9&amp;oh=1d95a6f78cccb1ae47547acaba8a068f&amp;oe=5C2EE63C"
      class="_k7v _2rgt _1j-f _2rgt _3n0b img" style="height: inherit;object-fit: inherit;width: inherit;object-fit: cover"
      id="u_a_5g" data-nt="NT:IMAGE"></div>
    <div class="_a5x _9_7 _2rgt _1j-f _2rgt" style="flex-grow:0;flex-shrink:1;top:12px;left:12px"
      id="u_a_5l" data-nt="NT:BOX_3">
      <div class="_9_7 _2rgt _1j-f _2rgt _2rgt _1j-f _2rgt" style="border-color: rgba(0,0,0,0.800000);border-radius: 4px;overflow: hidden;flex-grow:0;flex-shrink:1;padding:6px 6px 6px 6px;background-color:rgba(0,0,0,0.800000)"
        id="u_a_5k" data-nt="FB:BORDER">
        <div class="_59k _2rgt _1j-f _2rgt" style="font-size: 12px;font-weight: 400;color: #FFFFFF;text-shadow: 0.000000px 0.000000px 0.000000px rgba(0,0,0,0.000000)"
          id="u_a_5j" data-nt="FB:TEXT4"><span><span style="display: inline;text-decoration: " id="u_a_5i"><span>$1</span></span></span></div>
      </div>
    </div>
  </a>
</div>

There's a click handler on the parent div, and an inline onclick='return false' on its child <a>.

The div seems like it's calling some TimeSlice method that does some wacky stuff in https://static.xx.fbcdn.net/rsrc.php/v3iczx4/y7/l/en_US/aJlFVzNMGpl.js and then I guess it will end up calling whatever actually opens the new tab...haven't discovered that yet.

In Chrome, if i dispatch a click on the <a> via $0.click(), it does what I expect. It does not in Fennec. But I have some local event handler logging that proves a click is being sent to the div:

> click being sent to [object HTMLDivElement]

Dennis, any further insights here? It's OK for us to not nail the diagnosis, I think -- but any useful context we can give during outreach would be helpful (bonus points if we figure it out, of course).

Comment 3

[Stefan Deiac]

Hi, I tested this issue with OnePlus 5T	(Android 8.1.0) and the behavior it's same as on description.
I tried to do a regression-range but I can't find a good version. Last version tested was from 2016-05-01. Also on Chrome works properly.

Comment 4

[Sky Schubert [:skyschub]]

Tom, I've spend too much time hunting the event handler here. The way to go here is probably to find the location of where a window should be opened, and walk the stack backwards from there, as the JS is way to ... compressed to find anything here. Unfortunately, I haven't had any luck finding calls to window.open, not even with adding a listener via TinkerTester. Do you have any luck?

Comment 5

[Thomas Wisniewski [:twisniewski]]

This now seems to be working fine for me on Fennec 64.0.1. Dennis, can you confirm?

Comment 6

[Liz Henry (:lizzard)]

Sorina, can your team check on this for 68? Thanks!

Comment 7

[Sorina Florean [:sflorean]]

(In reply to Liz Henry (:lizzard) (use needinfo) from comment #6)

Sorina, can your team check on this for 68? Thanks!

Sure, Liz.
Stefan, can you take a look, please? Based on comment 3 you were able to reproduce it. Thanks!

Comment 8

[Stefan Deiac]

Hello,
I tried to reproduce this issue on the latest version of Nightly 68.0a1 (2019-04-17) using OnePlus 5T (Android 9) and Nexus 6P (Android 8.1.0) but without any success.
Due to my findings, I'll close this ticket as Worksforme, thanks.