Before adding more data, I would like to get some feedback if I am doing this correctly:

* Is this the correct file?
* Will this information be combined with the existing table (with type support)?

More lines will be added.

Travis already shows me some errors. (I have problems with running npm locally, so I did not see this before. I always get a git timeout when running npm install.)

travis is pleased now. Any human feedback to the questions above?

So sorry to take so long to comment on this. We had a conversation about how to model BCD for input elements a while ago, the main comment is here: #1698 (comment).

Essentially, the idea is to treat different input types more or less as if they were different elements, which seems to mesh better with how people treat them.

We would then not document attribute support at the input level, we'd document it at the level of the different types. (However we wouldn't document compat for the other attributes unless we need to (meaning, unless the compat story for the other attributes is different from the compat story for the type itself).)

At the moment this gives us compat tables like:

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/color#Browser_compatibility
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/range#Browser_compatibility
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#Browser_compatibility

...which seem quite usable to me.

I'm not against revisiting this choice if we think it's not working out well though.

Hi @SimonHeimberg, do you plan on responding or updating your PR based on the feedback from wbamberg?

Hi again, @SimonHeimberg. Thanks for your work on this. I'm assuming that you don't have time to get to this right now. I'm going to close this PR, but please feel free to reopen this in the future, if you get time to do so. Thanks again!