Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect fieldname meaning for "sex" #9600

Closed
pavankjadda opened this issue Aug 11, 2023 · 2 comments
Closed

Incorrect fieldname meaning for "sex" #9600

pavankjadda opened this issue Aug 11, 2023 · 2 comments

Comments

@pavankjadda
Copy link

https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute

"sex" Gender identity (e.g. Female, Fa'afafine)

The field name sex shows meaning as Gender identity. But in reality they are different

Sex:
Sex can be one of the following

  • Male
  • Female
  • Unknown

Gender:
Sex can be one of the following

  • Female
  • Male
  • Neither exclusively male or female
  • Other
  • Transgender Female
  • Transgender Male
  • Unknown
@pavankjadda pavankjadda changed the title ""sex" Gender identity (e.g. Female, Fa'afafine)" Incorrect fieldname meaning for "sex" Aug 11, 2023
@bathos
Copy link

bathos commented Aug 12, 2023

HTML doesn’t define specific values for this — it’s a text-type autocomplete hint, not an enum, and beyond specifying broad semantics it’s up to the user & user agent what will be done with it. Neither of the lists you’ve given make much sense, anyway (e.g. a transgender male person would typically describe his gender as “male”, not “transgender male”; intersex people exist; etc).

Though the hint keyword is “sex”, the word is not user-facing and the semantic hint it indicates is “gender”. Incidentally this is also what forms asking for “sex” historically have most often meant by it (whether they “realized it” or not). There are extraordinarily few circumstances where it would be appropriate to ask a user to indicate anything else, so there is no reason to introduce a separate hint here.

@annevk
Copy link
Member

annevk commented Aug 18, 2023

Indeed.

@annevk annevk closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants