Bug 285529
| Summary: | Passwords Button not showing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michał Buczek <michal> |
| Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | katy_suhr, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | iOS 18 | ||
Michał Buczek
- Open any sign-in page
If there are both an email/username and password field visible (e.g. on https://m.facebook.com/), tapping on either field does show the iOS-native "🔑 Passwords" button directly above the keyboard, as well as the Orion-native password autofill bar (black bar with blue text/icons) above it.
- If there is only an email/username field (e.g. https://twitter.com/i/flow/login), and you have to press some sort of "Next" or "Continue" button before entering your password, then tapping on the email/username field does not show the iOS-native "🔑 Passwords" button above the keyboard. Instead it seems to usually show the "suggested words" input accessory. The Orion-native password autofill bar will still show above this.
- The above behavior affects every 3rd-party browser I've tested on iOS, not just Orion. Safari seems to still show a Password input accessory even when they only see a single email/username field. That password input accessory is controlled 100% by the system, which seems to be why Orion, Chrome, Firefox, etc are all suffering the same issue.
More user details here in this thread https://orionfeedback.org/d/2026-icloud-passwords-not-showing/2
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/142885943>
katy_suhr
I'm not able to reproduce. Seems like this is an older thread. Is this behavior still reproducing for the originator?
Michał Buczek
(In reply to katy_suhr from comment #2)
> I'm not able to reproduce. Seems like this is an older thread. Is this
> behavior still reproducing for the originator?
Me neither, perhaps the website has changed since then