Closed
Bug 1888606
Opened 1 year ago
Closed 2 months ago
Login page is blank when accessed on co.my.xcelenergy.com with Strict ETP
Categories
(Web Compatibility :: Privacy: Site Reports, defect, P3)
Tracking
(firefox124 affected, firefox125 affected, firefox126 affected)
VERIFIED
WORKSFORME
People
(Reporter: ctanase, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: webcompat:tracker-blocking)
Attachments
(1 file)
|
1.45 MB,
video/mp4
|
Details |
Environment:
Operating system: Windows 10
Firefox version: Nightly 126.0a1 (2024-03-28)
Preconditions:
• ETP set to STRICT
• Clean profile
Steps to reproduce:
- Go to https://co.my.xcelenergy.com/s/
- Click on "Sing In" button displayed on the header.
- Observe the page.
Expected Behaviour:
The login page loads correctly.
Actual Behaviour:
The login page is blank when redirected.
Notes:
- Screen rec attached
- Reproducible on Firefox Release as well
- Not reproducible with Standard ETP
- Reproducible with both Standard and Strict ETP in Private mode
- The login form is missing with Strict ETP if the login page URL is accessed directly: https://my.xcelenergy.com/MyAccount/XE_Login?template=XE_MA_Template
| Reporter | ||
Updated•1 year ago
|
Blocks: tp-breakage
Comment 1•1 year ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
status-firefox125:
--- → affected
Updated•1 year ago
|
Severity: -- → S3
Updated•1 year ago
|
Component: Privacy: Anti-Tracking → Privacy: Site Reports
Product: Core → Web Compatibility
Updated•9 months ago
|
Keywords: webcompat:tracker-blocking
Comment 2•2 months ago
|
||
This seems to have been fixed in the meantime. Either by website change or by our blocklist change.
@Calin: Do you mind testing whether this also works for you?
Status: NEW → RESOLVED
Closed: 2 months ago
Flags: needinfo?(ctanase)
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 3•2 months ago
|
||
No longer an issue.
Status: RESOLVED → VERIFIED
Flags: needinfo?(ctanase)
You need to log in
before you can comment on or make changes to this bug.
Description
•