Closed
Bug 1475529
Opened 7 years ago
Closed 5 years ago
Unable to sign in/register account on www.harley-davidson.com while Tracking Protection strict is enabled
Categories
(Web Compatibility :: Site Reports, defect, P5)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: oanaarbuzov, Unassigned)
References
(Blocks 1 open bug, )
Details
(Whiteboard: tp-content)
User Story
gigya.com
Attachments
(2 files)
[Environment:]
Browser / Version: Firefox Nightly 62.0a1 (2018-07-11)
Operating System: Windows 10 Pro
[Steps to Reproduce:]
1. Navigate to https://www.harley-davidson.com/shop/mens-motorcycle-clothes
2. Click the “Sign in” button.
3. Select “Sign in” option.
4. Observe behavior.
[Expected Behavior:]
The “Login” overlay is displayed.
[Actual Behavior:]
Nothing happens, the “Login” overlay is not displayed.
[Note:]
1. Reproducible also for “Register” option.
2. Not reproducible with Tracking Protection basic.
Reporter | ||
Comment 1•7 years ago
|
||
Looking at the devtools console, here are the blocked resources:
The resource at “https://se.monetate.net/js/2/a-2535297b/p/harley-davidson.com/entry.js” was blocked because tracking protection is enabled.[Learn More] mens-motorcycle-clothes
The resource at “https://tags.bkrtx.com/js/bk-coretag.js” was blocked because tracking protection is enabled.[Learn More] mens-motorcycle-clothes
The resource at “https://libs.coremetrics.com/eluminate.js” was blocked because tracking protection is enabled.[Learn More] mens-motorcycle-clothes
The resource at “https://assets.adobedtm.com/dea66dda64873ee103a825b11f01324924689d32/satelliteLib-9796eb96024c431db5e76b60fcd5b1b62f5eaf07.js” was blocked because tracking protection is enabled.[Learn More] mens-motorcycle-clothes
The resource at “https://s.go-mpulse.net/boomerang/7KGT2-WV6WZ-J2T9H-7NEA3-52XMC” was blocked because tracking protection is enabled.[Learn More] mens-motorcycle-clothes
The resource at “https://www.google-analytics.com/analytics.js” was blocked because tracking protection is enabled.[Learn More] mens-motorcycle-clothes
The resource at “https://cdns.gigya.com/js/gigya.js?apikey=3_Gqzd0zsUdMuS9EkGrPWmFOM3hIuPd3-BK9O7b40IWZO9bkh_-I1E11vDJQFU3nOt&lang=en&_=1531414472232” was blocked because tracking protection is enabled.[Learn More] mens-motorcycle-clothes
The resource at “https://bs.serving-sys.com/BurstingPipe/ActivityServer.bs?cn=as&ActivityID=309687&rnd=570101.2909753271” was blocked because tracking protection is enabled.[Learn More]
So there were domains to test:
- se.monetate.net
- tags.bkrtx.com
- libs.coremetrics.com
- assets.adobedtm.com
- tags.bkrtx.com
- s.go-mpulse.net
- www.google-analytics.com
- cdns.gigya.com
- bs.serving-sys.com
I opened the URL in a fresh browser profile (Firefox Nightly 63, uMatrix installed, normal mode), loaded the page and tried to sign in/create account.
I disabled the Spoof Referrer option in uMatrix and then whitelisted different combination of the domains.
In the end I whitelisted:
- gigya.com (including all the linked domains and frames cdns.gigya.com)
and the "Log in" overlay was displayed was displayed.
So in conclusion:
- gigya.com – Content = [tp-content]
François could you confirm my findings?
Flags: needinfo?(francois)
Reporter | ||
Comment 2•7 years ago
|
||
Added uMatrix results.
Reporter | ||
Updated•7 years ago
|
Summary: Unable to sign in/register account while Tracking Protection strict is enabled → Unable to sign in/register account on www.harley-davidson.com while Tracking Protection strict is enabled
Comment 3•7 years ago
|
||
That looks great Oana, thanks!
As a minor point, I'd suggest putting just "gigya.com" in the user story field (instead of "cdns.gigya.com") since that's what's in the Disconnect list: https://github.com/mozilla-services/shavar-prod-lists/blob/f16248d7f33367bb3c48d72fb32fdb239dbe0c8e/disconnect-blacklist.json#L6677
User Story: (updated)
Flags: needinfo?(francois)
Updated•7 years ago
|
Priority: -- → P5
Assignee | ||
Updated•6 years ago
|
Product: Tech Evangelism → Web Compatibility
Comment 4•5 years ago
|
||
I'm able to create an account and/or log in while using strict mode on the most recent nightly build, so this ought to be fixed now.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•