Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

www.lequipe.fr - Match tabs are not working #18174

Closed
softvision-sergiulogigan opened this issue Aug 8, 2018 · 12 comments
Closed

www.lequipe.fr - Match tabs are not working #18174

softvision-sergiulogigan opened this issue Aug 8, 2018 · 12 comments
Labels
browser-firefox-mobile engine-gecko The browser uses the Gecko rendering engine priority-important severity-critical The site or core functionality is unusable, or you would probably open another browser to use it. status-first-contact
Milestone
fixed

Comments

@softvision-sergiulogigan
Copy link

URL: http://www.lequipe.fr/Football/match/363729

Browser / Version: Firefox Mobile Nightly 63.0a1 (2018-08-07)
Operating System: Windows 10
Tested Another Browser: Yes

Problem type: Site is not usable
Description: Match tabs are not working
Steps to Reproduce:

  1. Navigate to: http://www.lequipe.fr/Football/match/363729
  2. Click on the "AVANT-MATCH" / "RÉS - CLASS" / "STATS" tab.

Expected Behavior:
The tabs open.

Actual Behavior:
Nothing happens.

Notes:

  1. The issue is also reproducible on on Firefox 52 Release.
  2. The issue is not reproducible on Chrome 58.
  3. Screenshot attached.

Watchers:
@softvision-oana-arbuzov
@softvision-sergiulogigan

sv;

From webcompat.com with ❤️
@webcompat-bot webcompat-bot added this to the needstriage milestone Aug 8, 2018
@softvision-sergiulogigan softvision-sergiulogigan changed the title www.lequipe.fr - site is not usable www.lequipe.fr - Match tabs are not working Aug 8, 2018
@softvision-sergiulogigan
Copy link
Author

image

@IronJunkie
Copy link

I was able to reproduce this with FF61 on Win10 (worked fine on Edge)

I went to settings and turned off "tracking protection" reloaded page and then the tabs began to work, I then enabled privacy tracking again, reloaded page but the this time the tabs are still working. I restarted FF and it's still working now with with tracking set to ALWAYS. (workaround)

@karlcow
Copy link
Member

karlcow commented Aug 10, 2018

with a fresh profile, it just doesn't work.
events are set on the html element.

The tab is on when the class attribute active is set.

When we click on the tab, it requests first
https://connect.facebook.net/en_US/fbevents.js
to signal to… facebook…

Then goes to fetch an ad
https://fogl1onf.com/10301/b.js

create a tracking pixel.
https://www.lequipe.fr/elements/js/standalone/standalone/prebid.js

set up a video player
https://cdn.pulpix.com/static/pulpix.js

multiple more trackers and ads

and many ways to die before getting to the tab click.

Screenshot Description

@karlcow
Copy link
Member

karlcow commented Aug 10, 2018

When I click on ##ONG_AVMATCH, it seems to die with searchAd

click event fired on 
<a>
 
click { target: a
, buttons: 0, clientX: 245, clientY: 802, layerX: 245, layerY: 32 }
 
b()
​
length: 0
​
name: ""
​
prototype: Object { … }
​
<prototype>: function ()
eval:11:7
click event fired on 
<a>
 
click { target: a
, buttons: 0, clientX: 245, clientY: 802, layerX: 245, layerY: 32 }
 
handle()
​
arguments: null
​
caller: null
​
elem: <body class="Football" ds="20180810" sport="Football " data-codeweb="D1" data-idopta="853381" data-idmatch="363729" empreinte="" commente="1" cachelive="20180807144311" an="" ac="" bcl="1" total_bcl="4" init="1" data-prol="0" data-tab="0" minutejson="0">
​
length: 1
​
name: ""
​
prototype: Object { … }
​
<prototype>: function ()
eval:11:7
click event fired on 
<a>
 
click { target: a
, buttons: 0, clientX: 245, clientY: 802, layerX: 245, layerY: 32 }
 
handle()
​
arguments: null
​
caller: null
​
elem: HTMLDocument https://www.lequipe.fr/Football/match/363729
​
length: 1
​
name: ""
​
prototype: Object { … }
​
<prototype>: function ()
eval:11:7
click event fired on 
<a>
 
click { target: a
, buttons: 0, clientX: 245, clientY: 802, layerX: 245, layerY: 32 }
 
i()
​
arguments: null
​
caller: null
​
length: 1
​
name: "i"
​
prototype: Object { … }
​
<prototype>: function ()
eval:11:7
click event fired on 
<a>
 
click { target: a
, buttons: 0, clientX: 245, clientY: 802, layerX: 245, layerY: 32 }
 
searchAd()
​
arguments: null
​
caller: null
​
length: 1
​
name: "searchAd"
​
prototype: Object { … }
​
<prototype>: function ()

@karlcow
Copy link
Member

karlcow commented Aug 13, 2018

I'm not sure where/when it dies, but definitely somewhere in the trackers.
We probably should contact them. There is a race condition which seems to kick in one part of the code.

Moving to needscontact or even maybe contactready as we contacted them in the past.

@karlcow karlcow modified the milestones: needsdiagnosis, contactready Aug 13, 2018
@softvision-sergiulogigan
Copy link
Author

More context: https://bugzilla.mozilla.org/show_bug.cgi?id=1338483

Closed
@adamopenweb
Copy link
Collaborator

adamopenweb commented Aug 15, 2018 •
edited
Loading

I've reached out to them in #6576 but didn't get a response.

Edit: Looks like it might have been fixed though.

@adamopenweb
Copy link
Collaborator

Reaching out again to contact@lequipe.fr.

@adamopenweb adamopenweb modified the milestones: contactready, sitewait Aug 15, 2018
@softvision-sergiulogigan
Copy link
Author

The issue is still reproducible on my side, on a fresh profile, in Firefox Nightly 63, on Windows 10.

@softvision-sergiulogigan
Copy link
Author

The issue is still reproducible on my side, on a fresh profile, in Firefox Nightly 65, on Windows 10.

@miketaylr miketaylr added the engine-gecko The browser uses the Gecko rendering engine label Apr 30, 2019
@adamopenweb
Copy link
Collaborator

The page has changed for me.

@adamopenweb adamopenweb added severity-important A non-core broken piece of functionality, not behaving the way you would expect. severity-critical The site or core functionality is unusable, or you would probably open another browser to use it. and removed severity-important A non-core broken piece of functionality, not behaving the way you would expect. labels May 7, 2019
@softvision-sergiulogigan
Copy link
Author

The page has changed for me.

Yup...

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
browser-firefox-mobile engine-gecko The browser uses the Gecko rendering engine priority-important severity-critical The site or core functionality is unusable, or you would probably open another browser to use it. status-first-contact
Projects
None yet
Milestone
fixed
Development

No branches or pull requests
6 participants
@miketaylr @karlcow @adamopenweb @webcompat-bot @softvision-sergiulogigan @IronJunkie