Created attachment 8934722 [details] 2017-12-05 23_46_11-.png User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171112125346 Steps to reproduce: * go to https://www.lequipe.fr/Football/match/422947 * click on clickable tabs: AVANT-MATCH, RÉS - CLASS, STATS Actual results: nothing happens, the items are clickable but seems inactive Expected results: the content of the tab should be displayed
I can reproduce this report on my system and running Firefox in the safemode makes this work. To bad that I was away to long to remember what the safemode disables besides extensions :-(
@Matthias: good catch. indeed it seems that the issue is related to Adblock Plus add-on. I don't reproduce the issue if this add-on is disabled. so I don't know if it is a real bug. anyway thanks for your help.
actually I observe 2 different behavior * on my business laptop (win7 firefox ESR 52.2.1), disabling adblock plus only is sufficient to fix the issue * on my personal laptop (win10 firefox 57), running firefox in safe mode is necessary to fix the issue
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 I had tested this issue on Windows 10 x64 with latest Firefox Release(57.0.2) and the latest Nightly (59.0a1-20171207220423) with a clean new Firefox profile and manage to reproduce the issue. After navigating to the provided URL and clicking any of the mentioned tabs "AVANT-MATCH, RÉS - CLASS, STATS", the content for the corresponding tab is not displayed.
status-firefox57: --- → affected
status-firefox58: --- → affected
status-firefox59: --- → affected
Component: Untriaged → Event Handling
OS: Unspecified → All
Product: Firefox → Core
Hardware: Unspecified → All
Hi Emil, I tried Firefox 56 which worked well so I suspected this is a regression. Could you please help us get the regression window? Thanks.
Regression window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=10d42af6319d08daca29d5d163f301696b5ff1fd&tochange=b37a0bd71bbb1f3e5b4f58f1936d9cc0a38851d2 Regressed by: b37a0bd71bbb Honza Bambas — Bug 1358060 - Allow postponing of unimportant resources opening during page load, class-of-service Tail flag. r=dragana And also I confirmed that setting network.http.tailing.enabled=false fixes the problem on Nightly59.0a1.
Status: UNCONFIRMED → NEW
Component: Event Handling → Networking: HTTP
Ever confirmed: true
(In reply to Alice0775 White from comment #7) > Regression window: > https://hg.mozilla.org/integration/mozilla-inbound/ > pushloghtml?fromchange=10d42af6319d08daca29d5d163f301696b5ff1fd&tochange=b37a > 0bd71bbb1f3e5b4f58f1936d9cc0a38851d2 > > Regressed by: > b37a0bd71bbb Honza Bambas — Bug 1358060 - Allow postponing of unimportant > resources opening during page load, class-of-service Tail flag. r=dragana > > > And also I confirmed that setting network.http.tailing.enabled=false fixes > the problem on Nightly59.0a1. Thank you!
I'll look into this. Thanks for the report!
Assignee: nobody → honzab.moz
This is invalid. The site has to be fixed. They count on presumption that the twitter script is loaded before their script referencing twitter APIs. The twitter script is referenced as: <script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script> Hence, the order is not guarantied. Just check the web console, there is a bunch of "ReferenceError: twttr is not defined" errors. This breaks assigning the events on the tabs. When I turn off tailing they disappear, twitter.com/widgets.js loads on time. The site is also broken in Private Browsing windows and when Tracking Protection is turned always on.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
are you sure this issue is invalid? it is not reproduced with other browsers.
(In reply to amo.bordier from comment #11) > are you sure this issue is invalid? it is not reproduced with other browsers. Yes, I'm sure. The page functionality is dependent on timing that is not in any way synchronized. If the twitter server responses with a larger delay you will get the same issue. Please contact administrators of that web portal to fix their site.
Anyway we should switch to Chrome.
You need to log in before you can comment on or make changes to this bug.