mdn / mdn/browser-compat-data

`api.HTMLFormElement` - `api.HTMLFormElement` precedes support for `<form>`

Open
#24,135 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:safari data:api
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

I don't know this is conclusively wrong, but it is suspicious. The BCD for HTMLFormElement shows support earlier than <form> for Safari and Safari for iOS.

What browsers does this problem apply to, if applicable?

Safari

What did you expect to see?

I'd assume that the the API landed at the same time as the element. In other words, I'd expect both html.elements.form and api.HTMLFormElement to show Safari 3 and iOS 1 instead of ≤4 and ≤3.2 respectively.

Did you test this? If so, how?

I haven't tested it and I'm not sure how I would.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

See the generated status from web-features https://github.com/web-platform-dx/web-features/pull/1440

Do you have anything more you want to share?

@Elchi3 and @queengooborg: this is the kind of thing that I was talking about this morning. Let me know if this style of issue is OK, or how you'd like me to improve it.

MDN URL

No response

MDN metadata

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the generated status in web-platform-dx/web-features#1440 and compare the BCD entries for api.HTMLFormElement and html.elements.form. Verify the historical Safari and Safari for iOS support data before deciding whether the values should match; done means a justified data correction or a clear explanation of why they differ.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.