Missing HTML attributes meta issue

[rachelandrew]

In looking into #1510 realised we don't have docs for a whole bunch of attributes. I'm going to pick them off, but I thought I would list them here and if anyone else fancies writing one just add a comment.

The page that lists them is at: https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes

It is likely that some of these are documented but within details of the element they relate to, in that case it may just be that the link needs updating. At the moment all of these 404.

• accept-charset
• action
• align
• allow
• alt
• async
• autofocus
• autoplay
• buffered
• charset
• checked
• cite
• code
• codebase
• cols
• colspan
• content
• contextmenu
• controls
• coords
• data
• datetime
• decoding
• default
• defer
• dirname
• download
• enctype
• enterkeyhint
• for
• form
• formaction
• formenctype
• formmethod
• formnovaliddate
• formtarget
• headers
• high
• href
• hreflang
• http-equiv
• icon
• importance
• kind
• label
• language
• loading
• list
• loop
• low
• media
• method
• muted
• name
• novalidate
• open
• optimum
• placeholder
• poster
• preload
• referrer-policy
• reversed
• rows
• rowspan
• scope
• scoped
• selected
• shape
• sizes
• slot
• span
• src
• srcdoc
• srclang
• srcset
• start
• summary
• target
• type
• usemap
• value
• width
• wrap

[Ryuno-Ki]

Thank you so much!
Do you have a preferred „template” to structure the documents? (In case somebody is picking up an article)

Would there be value in „stubbed” articles which contain basic information, but perhaps lack certain details?

[rachelandrew]

There are guidelines in the docs, these are going to be similar to an HTML element reference page however being an attribute they will all be a little different to each other. The attributes don't apply to all elements, and apply differently depending on where they are used.

[Ryuno-Ki]

I just discovered #1707 also.

The mentioned guidelines likely refer to https://github.com/mdn/content#adding-a-new-document

However, I'm more concerned about the structure (like, which headlines should be included. What other data can be used? (Interactive Demos, BCD table etc), which links are apt for being shown in the „see also” part at the end).

This way, it comes down to „fill in the blanks” instead of thinking about how to start.
Copying from an existing document implies, that there is already an agreed upon format (which I cannot confirm).

[Elchi3]

I've been trying to get all the global attributes documented under https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes, however I wonder if It really makes sense to have a similar page tree for non-global attributes under https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes

If you document non-global attributes under that tree, then you get into the awkward situation of describing several uses of the attribute, like done on https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/for. So, what's the motivation for this page? Do people search for "html for attribute" and then need a disambiguation page? Wouldn't they rather want to search for "for label element" or so? The page reads to me like you would always need to go to either the <label> page or the <output> page if you want to really know about it. So, if we really want to populate such a tree for non-global attributes, how can we make the pages useful?

[rachelandrew]

@Elchi3 the page for for was exactly because someone was looking for information on for, so yes people are doing that.

It may be that some atts don't need their own page if we can have a way of linking to them within an element. Atts that only ever apply to one element for example, however atts that apply to some but not all elements I think there is a strong case for documenting. If a person is trying to use that attribute and it doesn't work, perhaps due to it not applying to the element they are using it on, they are very likely to search for the attribute.

[Ryuno-Ki]

@Aayushap1 is going to work on the async attribute page (perhaps also defer) and tracks the progress in #1899

@Ryuno-Ki you can assign this task to me

@Aayushap1 is going to work on the async attribute page (perhaps also defer) and tracks the progress in #1899

this one

[Elchi3]

@Elchi3 the page for for was exactly because someone was looking for information on for, so yes people are doing that.

Thanks for elaborating this some more, @rachelandrew! Makes sense to me then.

@Ryuno-Ki you can assign this task to me

@Aayushap1 looks like #1899 is already assigned to you. Cheers!

Ok sir

…

On Mon, 1 Feb 2021 at 3:19 PM, Florian Scholz ***@***.***> wrote: @Elchi3 <https://github.com/Elchi3> the page for for was exactly because someone was looking for information on for, so yes people are doing that. Thanks for elaborating this some more, @rachelandrew <https://github.com/rachelandrew>! Makes sense to me then. @Ryuno-Ki <https://github.com/Ryuno-Ki> you can assign this task to me @Aayushap1 <https://github.com/Aayushap1> looks like #1899 <#1899> is already assigned to you. Cheers! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1712 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASU7H6EHSHMF752SZRGFIQ3S4Z2MJANCNFSM4WRTEP2A> .

[Ryuno-Ki]

Dear @Aayushap1,
I just came back from my work. Give me some minutes to check the PR.
Thanks for your patience.

[Ryuno-Ki]

Okay, it looks like you confused some bits: https://github.com/Aayushap1/content/pull/1
The PR needs to go against mdn/content and not against the fork you've opened to add changes.

Or perhaps the PR is #1943 ?