jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Update article.md

Browse source 
Changed 'XHTML' to 'in XML mode' in title to match contents. 'XHTML' isn't mentioned anywhere else in the article except in that title. So either change it to 'XML' or explain the relationship?
This commit is contained in:
paroche 2019-10-17 23:10:07 -06:00 • committed by GitHub
parent eb2b6c9514
commit 4452139ca0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
2-ui/1-document/05-basic-dom-node-properties/article.md
View file

@ -187,7 +187,7 @@ For instance, let's compare `tagName` and `nodeName` for the `document` and a co
If we only deal with elements, then we can use both `tagName` and `nodeName` - there's no difference. If we only deal with elements, then we can use both `tagName` and `nodeName` - there's no difference.
```smart header="The tag name is always uppercase except XHTML" ```smart header="The tag name is always uppercase except in XML mode"
The browser has two modes of processing documents: HTML and XML. Usually the HTML-mode is used for webpages. XML-mode is enabled when the browser receives an XML-document with the header: `Content-Type: application/xml+xhtml`. The browser has two modes of processing documents: HTML and XML. Usually the HTML-mode is used for webpages. XML-mode is enabled when the browser receives an XML-document with the header: `Content-Type: application/xml+xhtml`.
In HTML mode `tagName/nodeName` is always uppercased: it's `BODY` either for `<body>` or `<BoDy>`. In HTML mode `tagName/nodeName` is always uppercased: it's `BODY` either for `<body>` or `<BoDy>`.