Remove JsDocs Warnings

[jesdaigle]

Per TF meeting, remove JsDoc warning.

[mcking65]

Per group discussion on today, run the autofix

[css-meeting-bot]

The ARIA Authoring Practices (APG) Task Force just discussed Remove JsDocs Warnings #2039.

The full IRC log of that discussion

<Jem> Topic:Remove JsDocs Warnings #2039
<jamesn> github: https://github.com//issues/2039
<siri_> Rich: Js.doc, is warning about blank *, white space, as discussion few days ago about auto fixes
<siri_> MK: They were showing up on the files tab, hope everyones comments are wrt JS.doc
<siri_> Howard has no questions

[howard-e]

As stated discussion yesterday:

Rich: Js.doc, is warning about blank *, white space, as discussion few days ago about auto fixes
MK: They were showing up on the files tab, hope everyones comments are wrt JS.doc

@mcking65 not seeing those warnings currently or able to reproduce. Is there any example you could point me to for further help? Otherwise, maybe this has been resolved and we can close this issue

The only thing I can see is the following lint-html errors. But these warnings seem to all be acceptable based on the comments before these lines in the code:

• The “banner” role is unnecessary for element “header”. [examples/treeview/treeview-navigation.html#L66]
• Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools). [examples/treeview/treeview-navigation.html#L323]
• The “contentinfo” role is unnecessary for element “footer”. [examples/treeview/treeview-navigation.html#L332]
• The “banner” role is unnecessary for element “header”. [examples/menubar/menubar-navigation.html#L64]
• Consider using the “h1” element as a top-level heading only (all “h1” elements are treated as top-level headings by many screen readers and other tools). [examples/menubar/menubar-navigation.html#L233]
• The “contentinfo” role is unnecessary for element “footer”. [examples/menubar/menubar-navigation.html#L242]

[nschonni]

Think it was already fixed in #2032

[mcking65]

closed by #2032