Logitech Support login page doesn't fully load
Categories
(Core :: Privacy: Anti-Tracking, defect, P3)
Tracking
()
People
(Reporter: arcooke, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [tp-needsrepro])
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
- Visit https://support.logitech.com
- Click the Sign In link in the top header nav
Actual results:
- Login form doesn't load: https://i.imgur.com/f894Lzq.png
Expected results:
It loads fine in Chrome: https://i.imgur.com/wd7OAmy.png
In both browsers, I tested in private browsing mode with extensions disabled. There are no errors or warnings in the F12 console
Nightly 69.0a1 (2019-06-30) on Linux
Well that's odd. I wasn't getting warnings before, but now I am.
https://i.imgur.com/RoSwI1S.png
Seems to maybe be a facebook tracker preventing the loading, though it still happens with trackers disabled.. not sure if that's intended.
Comment 2•5 years ago
|
||
Hi @arcooke, tested the issue and here are the results:
[Platforms tested]: Ubuntu 18.04, Windows 10, Mac OS X.
[FF environments]: Nightly 69.0a1, beta 68.0b14, release 67.0.4
- on all machines and ff versions the issue cannot be reproduced.
Additionally, please provide me all your extensions installed, could the possibility of a conflict.
I will set a component, if isn't the proper one please fell free to change it.
Thanks.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0
Got the same issue. Tried Private Window with all addons disabled problem is still there.
Comment 4•5 years ago
|
||
I don't know how this ended up in Layout. I can reproduce. Disabling Tracking Protection fixes it.
Ehsan is this the right component for TP bugs?
Comment 5•5 years ago
|
||
This can be reproduced with Strict Content Blocking or in Private Browsing mode, so it is caused by Tracking Protection.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 6•5 years ago
|
||
Confirmed. When I click their sign-in page (the base page loads without any obvious breakage). This is because their code is relying on Facebook's SDK loading properly before it considers the form ready to show. The potential work-around in bug 1226498 fixes this.
Description
•