W3C != W3schools
First I would like to mention that it is a very common thing for those who begin to study and ask questions on google, W3schools has no connection with W3C or W3.org, they only use the similar name to say that they teach things contained in W3C, but that doesn’t mean they teach correctly or just HTML/CSS/XML.
W3schools has also been known for the numerous flaws in its examples and tutorials, as well as misinterpreted explanations about some technologies
Today we can say that most of the errors in W3schools have been corrected, but it doesn’t mean that it is official or that it has good examples
About the attributes supported by the tag <html>
, it’s not because an attribute is incorrect in a tag that it won’t work, technologies like HTML, JS and CSS work in a similar way in all current browsers, but it doesn’t mean that W3.org implemented them, for example it is not because w3c released HTML5 that it will work equally in all browsers, the W3C is just a kind of "regulator" (who standardizes the technologies) to prevent many differences from arising between browsers which would hinder the development of websites (this has occurred in the past the famous Browser Wars, which goes beyond who is the most used, why one browser wanted to be better than the other creating technologies that were not standards, so it generated a lot of headache).
As I quoted in a comment, you do not need to know the A,B,C of the functioning of something, but seek it in the moment of need. The only utility I see to learn which attributes are all supported by a tag is if you:
- Will create a Crawler
- You will create a Javascript library that manipulates the DOM for a very specific purpose
If it’s not quite that, or better if you’re just creating pages to navigate in conventional browsers, then stick to doing the basic and intermediate, if you need something advanced like Opengraph from facebook then you can apply normally, don’t worry big sites like they wouldn’t create a flawed HTML/XML "schema", this would "burn their movie".
There is the use of Microdata or Rdfa which at one time can obstruct HTML if it fails at some point in typing (human error) and for this reason JSON-LD was created, as I mentioned here: What is the "application/Ld+json" type for in a <script tag>? But if you do it carefully and carefully you can still do it without obstructing the code, I mean use something when necessary, there are not many reasons to understand the interface deep down.
The link https://www.w3.org/TR/html-markup/html.html#html html leads east https://www.w3.org/TR/html-markup/global-attributes.html
Core:
accesskey
, class
, contenteditable
, contextmenu
, dir
, draggable
, dropzone
, copy
, move
, link
, hidden
, id
, lang
, spellcheck
, style
, tabindex
, title
and translate
Events:
onabort
, onblur
, oncanplay
, oncanplaythrough
, onchange
, onclick
, oncontextmenu
, ondblclick
, ondrag
, ondragend
, ondragenter
, ondragleave
, ondragover
, ondragstart
, ondrop
, ondurationchange
, onemptied
, onended
, onerror
, onfocus
, oninput
, oninvalid
, onkeydown
, onkeypress
, onkeyup
, onload
, onloadeddata
, onloadedmetadata
, onloadstart
, onmousedown
, onmousemove
, onmouseout
, onmouseover
, onmouseup
, onmousewheel
, onpause
, onplay
, onplaying
, onprogress
, onratechange
, onreadystatechange
, onreset
, onscroll
, onseeked
, onseeking
, onselect
, onshow
, onstalled
, onsubmit
, onsuspend
, ontimeupdate
, onvolumechange
and onwaiting
XML:
xml:lang
, xml:space
and xml:base
But I must remember, nay is because the attribute oncanplaythrough
this listed is that it will work and nay is because the attribute disabled
nay this listed that will not work (it is very likely to work), the operation in each browser may occur in a totally different way from other (although today most are working well standardized)but it is not because the browser supports something that this use is valid according to the standardization.
In short pattern is a thing, work is another. However I always prefer to try to follow the pattern to the maximum and on rare occasions make use of some hack (as the common case in CSS) that is not standard to help achieve a goal, often due to lack of some functionality in a given browser.
disabled in the <html> tag?? What would be the use of this?
– user28595
Has some attributes common to any element. The element
html
has only an additional specific attribute - that up to the moment I didn’t even know existed.– bfavaretto
@Diegof really do not see usefulness, like many other attributes. I am an advocate of the end of attributes without explanation of existence. But if they exist, one day they may appear in some code. I believe you already knew it existed. But, what about when we come across attributes that we have never seen? Whenever I look at a code I see an attribute that we study did not appear.. : ( It is neither by use, but by the will to know that there are... thank you.
– Ingrid Farabulini
@bfavaretto but the question is to know only the possible attributes in the element (tag) html and not in all possible elements in HTML5.
– Ingrid Farabulini
I had misunderstood, sorry. In this case it is not wide even. The most reliable answer is in the HTML specification, maintained by W3C (which is unrelated to w3schools, although many people fall for this).
– bfavaretto
I edited my first comment, adding a link to more
– bfavaretto