Hello, Bitwarden community,
I’m drafting a proposal for WHATWG to allow URI-based autocomplete values, which would let password managers like Bitwarden reliably identify form fields beyond the standard set (name, email, password, etc.).
Why this matters for Bitwarden:
Bitwarden already stores data types that browsers don’t autofill—passport numbers, driver’s licenses, frequent flyer numbers, rewards program IDs, and more. Currently, detecting these fields requires heuristics (scanning labels, field names, placeholders), which is fragile and locale-dependent.
This proposal would let site authors explicitly declare field intent:
<input type="text" autocomplete="https://schema.org/taxID"> <!-- SSN/ITIN -->
<input type="text" autocomplete="https://www.wikidata.org/wiki/Property:P12361"> <!-- Bluesky handle -->
Bitwarden could then match stored items to fields with certainty instead of guessing.
What I’m asking:
I’m not asking for a commitment to implement—just a signal of interest I can reference in the proposal. Something like “Bitwarden would find this useful” is enough.
The proposal leverages existing vocabularies (Schema dot org, Wikidata) so there’s no new registry to maintain. It’s fully backwards compatible—browsers already ignore unknown autocomplete values. Happy to discuss or adjust based on your feedback.
Thank you!
Pedro