discover.com - Unable to log in
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:7, firefox144 affected)
| Tracking | Status | |
|---|---|---|
| firefox144 | --- | affected |
People
(Reporter: bj, Unassigned)
References
(Depends on 1 open bug, )
Details
(5 keywords)
User Story
platform:windows,mac,linux,android impact:blocked configuration:rare affects:all branch:release diagnosis-team:webcompat user-impact-score:600
Attachments
(3 files)
The error message shown
I was previously able to log into discover.com but it no longer works. See the attached screenshot. My account is fine, I can log in with older versions of Firefox or from the app.
Here is the unhelpful output from mozregression:
6:03.66 INFO: Narrowed integration regression window from [26a4b3bb, ced0a433] (3 builds) to [39f0dc0f, ced0a433] (2 builds) (~1 steps left)
6:03.66 INFO: No more integration revisions, bisection finished.
6:03.66 INFO: Last good revision: 39f0dc0f24d549dd713351d8c6f84fab09227dce
6:03.66 INFO: First bad revision: ced0a433f4160325c8f7124c6112483e87cd3244
6:03.66 INFO: Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=39f0dc0f24d549dd713351d8c6f84fab09227dce&tochange=ced0a433f4160325c8f7124c6112483e87cd3244
6:07.06 INFO: ************* Switching to autoland by process of elimination (no branch detected in commit message)
6:09.11 ERROR: Unable to exploit the merge commit. Origin branch is mozilla-central, and the commit message for ced0a433 was:
No Bug - Update configs after merge day operations a=release
IGNORE BROKEN CHANGESETS
CLOSED TREE
|
||
Comment 1•11 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
Reporter | |
Comment 2•11 months ago
|
||
This happened on a Linux notebook computer, not Android.
|
|
Reporter | |
Comment 3•11 months ago
|
||
|
|
Reporter | |
Comment 4•11 months ago
|
||
|
||
Comment 5•11 months ago
|
||
Here is the unhelpful output from mozregression:
Since the push is a version bump, that's less unhelpful than you'd think - they might be one of the sites that allow-list specific browser versions.
|
||
Comment 6•11 months ago
|
||
I can log in with 144, no problem. I tried forcing my UA string to say firefox 145, still can log in.
BJ: Can you retry? They may have fixed it.
|
|
Reporter | |
Comment 7•11 months ago
|
||
Yep, I can log in. They probably fixed it.
Description
•