Open
Bug 1923588
Opened 4 months ago
Updated 24 days ago
icloud.com - Missing "Sign in with Passkey" option
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(Webcompat Priority:P2, firefox131 affected, firefox133 affected)
NEW
Webcompat Priority | P2 |
People
(Reporter: rbucata, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:product][webcompat:sightline])
User Story
platform:windows,linux impact:feature-broken configuration:general affects:all branch:release
Attachments
(1 file)
102.37 KB,
image/png
|
Details |
Environment:
Operating system: Windows 11
Firefox version: Firefox 130.0.1 (release)
Preconditions:
- Clean profile
Steps to reproduce:
- Navigate to: https://www.icloud.com/
- Click on the "Sign in" button
- Input a valid email account and press "Enter" on the keyboard
- Observe
Expected Behavior:
"Sign in with Passkey" and "Continue with Password" option buttons are present
Actual Behavior:
The password field is present
Notes:
- Reproducible on the latest Firefox Release and Nightly
- Reproducible regardless of the ETP setting
- Works as expected using Chrome
Created from webcompat-user-report:0c772475-b382-4135-899d-bb5972202ac3
Reporter | ||
Updated•4 months ago
|
status-firefox131:
--- → affected
status-firefox133:
--- → affected
Updated•4 months ago
|
Severity: -- → S4
User Story: (updated)
Depends on: 1838015
Keywords: webcompat:platform-bug
Priority: -- → P3
Comment 1•3 months ago
|
||
My best guess here is that iCloud.com is using the new getClientCapabilities
method to determine whether the platform supports the hybrid transport.
Depends on: 1884466
Comment 2•3 months ago
|
||
Actually, I'm able to get the "Sign in with a Passkey" option by just switching my user agent to match Chrome >= 113.
No longer depends on: 1884466
Updated•3 months ago
|
Whiteboard: [webcompat-source:product] → [webcompat-source:product][webcompat:sightline]
Updated•24 days ago
|
Webcompat Priority: --- → P2
You need to log in
before you can comment on or make changes to this bug.
Description
•