From 4452139ca00ffa97648f70f3e2cfbf26f61087d7 Mon Sep 17 00:00:00 2001 From: paroche <46547072+paroche@users.noreply.github.com> Date: Thu, 17 Oct 2019 23:10:07 -0600 Subject: [PATCH] Update article.md 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? --- 2-ui/1-document/05-basic-dom-node-properties/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/2-ui/1-document/05-basic-dom-node-properties/article.md b/2-ui/1-document/05-basic-dom-node-properties/article.md index 6c0053d0..421a5aa6 100644 --- a/2-ui/1-document/05-basic-dom-node-properties/article.md +++ b/2-ui/1-document/05-basic-dom-node-properties/article.md @@ -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. -```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`. In HTML mode `tagName/nodeName` is always uppercased: it's `BODY` either for `` or ``.