classifies button-element web feature

[ChrisC]

Web feature docs: https://github.com/web-platform-dx/web-features/blob/main/features/button.yml

---

As of 2025-12-05, the wpt-pr-bot is requesting reviews from code owners for changes to WEB_FEATURES.yml files. To learn more about the purpose of these files, check out this presentation from TPAC 2025, Annotating WPT to Surface the Status of the Platform

[tkent-google]

Should we exclude these tests from the button feature?

[ChrisC]

Good question! Generally, we've been trying to avoid mapping tests to multiple web features, but I wonder if web features for HTML elements should be an exception to that practice? cc @foolip

I see that the dialog element is mapped to dialog and to various other related web features, for example. So perhaps we should do something similar here?

[foolip]

Generally we have tried to identify the primary feature being tested instead of allowing overlapping tests.

In this case the tests for constraint validation are spread across directories, but I think do make sense as currently mapped:
https://wpt.fyi/results/html/semantics?label=experimental&label=master&aligned&q=feature%3Aconstraint-validation

So I think it's best to exclude these tests from the <button> tests, and that we should do the same for <dialog> too ideally.