browser-compat-data icon indicating copy to clipboard operation
browser-compat-data copied to clipboard

HTML/Attributes/required has missing spec information

Open gijsk opened this issue 2 years ago • 5 comments

MDN URL

https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/required

What specific section or headline is this issue about?

Specifications + Browser compatibility

What information was incorrect, unhelpful, or incomplete?

This information is missing entirely.

What did you expect to see?

Correct information that links to the relevant spec. :-)

Do you have any supporting links, references, or citations?

No response

Do you have anything more you want to share?

No response

MDN metadata

Page report details
  • Folder: en-us/web/html/attributes/required
  • MDN URL: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/required
  • GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/html/attributes/required/index.md
  • Last commit: https://github.com/mdn/content/commit/942a529383ee7ee3996fb234187641c08935f3ff
  • Document last modified: 2023-04-13T06:13:15.000Z

gijsk avatar Nov 14 '23 13:11 gijsk

I've moved this to BCD because there is no information to link to. required is not a global attribute but should be present on a set of elements, including text, search, email etc. The problematic one being input as the presence will depend on the type of input.

When those exist they links could be added to the page metadata as browser compat. Right now only two of the values are supported, so you could add:

browser-compat: 
  - html.elements.select.required
  - html.elements.textarea.required

@queengooborg Thoughts on how to get this data in?

hamishwillee avatar Nov 17 '23 00:11 hamishwillee

Independently of the pertinence of such attribute pages, or even to display BCD on them, the fundamental underlying BCD problem is that the "basic support" entry in BCD doesn't tell what this basic support is. I'm cc/ @elchi3 because we discussed this in our 1:1.

Should we have an extra entry for basic support telling us what it encompasses? Like:

  • a formal syntax for CSS (the one done in basic support)
  • an array of member names for API
  • an array of attributes for HTML (SVG, MathML)

(I assume individually listing all of them is a bit overkill)

Something like:

{
  "html": {
    "elements": {
      "select": {
        "__compat": {
          "mdn_url": "https://developer.mozilla.org/docs/Web/HTML/Element/select",
          "spec_url": "https://html.spec.whatwg.org/multipage/form-elements.html#the-select-element",
          "basic": [ ... list of attributes that were there from the beginning … ]
          "support": {

teoli2003 avatar Nov 17 '23 06:11 teoli2003

OK. I don't mind how we do it as long as there is a clear story on what I should do :-)

hamishwillee avatar Nov 19 '23 23:11 hamishwillee

html.elements.select.required

also html.elements.input.required, which is adding via #21874

skyclouds2001 avatar Jan 09 '24 07:01 skyclouds2001

I've moved this to BCD because there is no information to link to. required is not a global attribute but should be present on a set of elements, including text, search, email etc. The problematic one being input as the presence will depend on the type of input.

When those exist they links could be added to the page metadata as browser compat. Right now only two of the values are supported, so you could add:

browser-compat: 
  - html.elements.select.required
  - html.elements.textarea.required

@queengooborg Thoughts on how to get this data in?

Agree this should be the best way to fix by adding the browser-compat key

skyclouds2001 avatar Jan 30 '24 16:01 skyclouds2001