Extract HTML `<datalist>` input type subfeatures by caugner · Pull Request #28189 · mdn/browser-compat-data

caugner · 2025-10-14T12:23:54Z

Summary

Extracts HTML <datalist> input type subfeatures, and duplicates these below html.input.elements.type_*.

Test results and supporting details

To review, look at "grouped by change" in this comment.

Related issues

Fixes #17480.

Once landed, we can tackle the issues mentioned in #25723.

github-actions · 2025-10-14T12:24:59Z

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

caugner

Note to myself: Missing spec URLs.

Elchi3

and duplicates these below html.input.elements.type_*.

I'm not sure if this is needed, is it?

caugner · 2025-10-17T11:58:33Z

and duplicates these below html.input.elements.type_*.

I'm not sure if this is needed, is it?

I would argue that the duplication is helpful for web developers that are looking at the input types. Recently, we used a similar approach for CSS transition, and IIRC we have a few related cases where a BCD feature relates to two APIs features.

In this case, the duplication helped me ensure the data is correct.

I could imagine adding a requires property to link these subfeatures to each other, ensuring they are within the support version range both of their parent feature, and the linked "required" feature.

Edit: That said, if you prefer that I delete the duplicates, I can drop them.

Elchi3 · 2025-10-17T14:04:11Z

I would like a second opinion if the duplication makes sense. Maybe @ddbeck?

ddbeck

I don't love the duplication, though I can kinda-sorta see a way of doing it that is more idiomatic:

The subfeatures of the html.elements.input.* features ought to be named list, representing support for the list attribute on that type. Since we treat the input types as if they were different elements, we can represent support for list as if it was an attribute unique to each input type (i.e., act as though <input type="color"> is <input-color>, then the subfeature is <input-color list="…">.

In this scenario, the duplication would be at the point of html.elements.datalist.input_type_*. Since <datalist> is the new thing, I think duplicating this data on html.elements.datalist makes sense as a convenience to MDN readers.

If we do this, I think there's a case to be made to remove html.elements.input.list as needless duplication (since it would be a duplicate of html.elements.input.text.list) and confusing (does it mean support for all types? At least one? Something else?).

(This makes me wish we had some sort of annotation in the data, something like canonical: "html.elements.input.color.list" on keys that duplicate other keys.)

ddbeck · 2025-10-17T14:44:50Z

html/elements/datalist.json

-                "version_added": "4",
-                "version_removed": "110",
-                "partial_implementation": true,
-                "notes": "The `<datalist>` element will only create a dropdown for textual types, such as `text`, `search`, `url`, `tel`, `email` and `number`. The `date`, `time`, `range` and `color` types are not supported."


Not all of the types mentioned in the note are represented by the subfeatures. The PR title had me anticipating keys like this:

html.elements.datalist

html.elements.datalist.input_type_color

html.elements.datalist.input_type_date

html.elements.datalist.input_type_email

html.elements.datalist.input_type_number

html.elements.datalist.input_type_range

html.elements.datalist.input_type_search

html.elements.datalist.input_type_tel

html.elements.datalist.input_type_text

html.elements.datalist.input_type_time

html.elements.datalist.input_type_url

This PR only extracts these four from existing data:

html.elements.datalist.input_type_color

html.elements.datalist.input_type_date

html.elements.datalist.input_type_range

html.elements.datalist.input_type_time

The current data suggests to me the following textual types were always supported:

html.elements.datalist.input_type_email

html.elements.datalist.input_type_number

html.elements.datalist.input_type_search

html.elements.datalist.input_type_tel

html.elements.datalist.input_type_text

html.elements.datalist.input_type_url

To clarify, this PR only extracts subfeatures for types currently mentioned data, without researching/collecting/adding data for other types not currently mentioned.

OK. I won't stand in the way of merging on this, but I would like to see an issue filed to complete the missing data.

(I would still like @Elchi3's review before I approve the PR overall, as it does imply some things that are not in the PR and it'd be nice to have consensus before proceeding in an incomplete state.)

Filed #28468.

Yeah, seems sad that this PR doesn't add the complete list of input types support. The issue is filed, though, so I won't stand in the way either.

caugner · 2025-12-12T16:41:20Z

@Elchi3 Please take a look at this PR when you have a moment. It would be nice to land this change. 🙏

caugner · 2026-01-30T16:31:06Z

@ddbeck If you find time to review this, that would be lovely. 🙏

github-actions · 2026-02-02T13:23:41Z

This pull request has merge conflicts that must be resolved before it can be merged.

caugner · 2026-02-03T16:16:11Z

Merged main incorporating the changes from #28915, see: https://redirect.github.com/mdn/browser-compat-data/pull/28189/commits/06bb9c6ee179785fb387f0c6768fa41eeb8a8626

As previously mentioned, I will tackle the remaining missing types separately.

Elchi3 · 2026-02-09T13:53:40Z

The subfeatures of the html.elements.input.* features ought to be named list, representing support for the list attribute on that type.

okay, this convinced me.

caugner requested a review from Elchi3 October 14, 2025 12:23

github-actions bot added data:html Compat data for HTML elements. https://developer.mozilla.org/docs/Web/HTML size:l [PR only] 101-1000 LoC changed labels Oct 14, 2025

caugner added 4 commits October 14, 2025 14:36

Extract HTML <datalist> input type subfeatures

8ad427d

Duplicate datalist subfeatures into input type data

2dcde74

Fix datalist data based on input type support data

d250c0f

Tag datalist subfeatures

3d54188

caugner force-pushed the datalist-types branch from 360ac12 to 3d54188 Compare October 14, 2025 12:36

caugner commented Oct 14, 2025

View reviewed changes

Elchi3 reviewed Oct 15, 2025

View reviewed changes

Add spec URLs for dataset features

a430cbe

caugner requested a review from Elchi3 October 17, 2025 11:59

ddbeck reviewed Oct 17, 2025

View reviewed changes

Rename datalist => list features

9737c85

caugner requested review from ddbeck and removed request for Elchi3 November 4, 2025 13:21

caugner removed the request for review from ddbeck November 12, 2025 11:23

caugner mentioned this pull request Nov 17, 2025

html.elements.datalist - Add missing input type subfeatures #28468

Closed

caugner requested review from Elchi3 and ddbeck January 13, 2026 15:13

caugner mentioned this pull request Jan 26, 2026

Update Firefox support for HTML datalist element #28915

Merged

github-actions bot added the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Feb 2, 2026

github-actions bot removed the merge conflicts 🚧 This PR needs to merge latest "main" branch to resolve a merge conflict or other issue. label Feb 3, 2026

caugner force-pushed the datalist-types branch from aca15ce to dbf1f5d Compare February 3, 2026 16:14

Merge branch 'main' into datalist-types

06bb9c6

caugner force-pushed the datalist-types branch from dbf1f5d to 06bb9c6 Compare February 3, 2026 16:14

Elchi3 approved these changes Feb 9, 2026

View reviewed changes

caugner merged commit 5b954d0 into main Feb 9, 2026
13 checks passed

caugner deleted the datalist-types branch February 9, 2026 14:34

mdn-bot mentioned this pull request Feb 9, 2026

Release v7.3.2 #28991

Merged

Conversation

caugner commented Oct 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test results and supporting details

Related issues

Uh oh!

github-actions bot commented Oct 14, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

caugner left a comment

Choose a reason for hiding this comment

Uh oh!

Elchi3 left a comment

Choose a reason for hiding this comment

Uh oh!

caugner commented Oct 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Elchi3 commented Oct 17, 2025

Uh oh!

ddbeck left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ddbeck Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

caugner Oct 17, 2025

Choose a reason for hiding this comment

Uh oh!

caugner Nov 7, 2025

Choose a reason for hiding this comment

Uh oh!

ddbeck Nov 10, 2025

Choose a reason for hiding this comment

Uh oh!

caugner Nov 17, 2025

Choose a reason for hiding this comment

Uh oh!

Elchi3 Feb 9, 2026

Choose a reason for hiding this comment

Uh oh!

caugner commented Dec 12, 2025

Uh oh!

caugner commented Jan 30, 2026

Uh oh!

github-actions bot commented Feb 2, 2026

Uh oh!

caugner commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Elchi3 commented Feb 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

caugner commented Oct 14, 2025 •

edited

Loading

github-actions bot commented Oct 14, 2025 •

edited

Loading

caugner commented Oct 17, 2025 •

edited

Loading

ddbeck left a comment •

edited

Loading

caugner commented Feb 3, 2026 •

edited

Loading