What shall we do with the Constraint Validation API?

[wbamberg]

I spent a bit of time today fixing Web/API overview pages that erroneously use {{APIRef}} instead of {{DefaultAPISidebar}}: mdn/content#22468.

In a a couple of places I had to add a new group to GroupData. I have fixed all of them except the Constraint Validation API (https://developer.mozilla.org/en-US/docs/Web/API/Constraint_validation). This one is problematic for a couple of reasons:

• although it only defines one interface (ValidityState) it extends lots of existing HTML interfaces in a very repetitive way
• it doesn't have its own spec (which these things usually should have), it seems to be part of the HTML standard

I think rather than trying to craft a group for it, we should treat it as part of the "HTML DOM API". Actually the GroupData for HTML DOM already contains ValidityState, so we wouldn't need any GroupData updates at all.

The only think we might want to do is convert the guide-y parts of https://developer.mozilla.org/en-US/docs/Web/API/Constraint_validation into a short guide to constraint validation, and put it under https://developer.mozilla.org/en-US/docs/Web/API/HTML_DOM_API.

WDYT?

[Rumyra]

Yeh this sounds like a good plan @wbamberg

[wbamberg]

-> mdn/content#22525