


Discuss in detail the basic properties of DOM in javascript_javascript skills
Structure and content attributes
nodeType
All nodes have types, and there are a total of 12 types of nodes.
interface Node {
// NodeType
const unsigned short ELEMENT_NODE = 1;
const unsigned short ATTRIBUTE_NODE = 2;
const unsigned short TEXT_NODE = 3;
const unsigned short CDATA_SECTION_NODE = 4;
const unsigned short ENTITY_REFERENCE_NODE = 5;
const unsigned short ENTITY_NODE = 6;
const unsigned short PROCESSING_INSTRUCTION_NODE = 7;
const unsigned short COMMENT_NODE = 8;
const unsigned short DOCUMENT_NODE = 9;
const unsigned short DOCUMENT_TYPE_NODE = 10;
const unsigned short DOCUMENT_FRAGMENT_NODE = 11;
const unsigned short NOTATION_NODE = 12;
...
}
The two most important nodes are the element node (1) and the text node (3). The rest are rarely used.
For example, when listing all child element nodes, we can iterate over it and use childNodes[i].nodeType != 1 to detect.
The following is the implementation code:
- John
- Bob
<script> <br /> var childNodes = document.body.childNodes<br /> for(var i=0; i<childNodes.length; i ) {<br /> if (childNodes[i].nodeType != 1) continue<br /> alert(childNodes[i])<br /> }<br /> </script>
*Thinking
What will the following code prompt:
<script><br /> alert(document.body.lastChild.nodeType)<br /> </script>
nodeName, tagName
Both nodeName and tagName contain the name of the node.
For document.body
alert( document.body.nodeName ) // BODY
All nodeNames in HTML will be capitalized.
When nodeName is not capitalized
This situation is relatively rare, if you are curious you can read below.
As you probably already know, browsers have two ways of parsing: HTML mode and __XML mode. Usually the HTML schema is used, but when the XMLHttpRequest__ technology is used to obtain an XML document, the XML schema is used.
XML mode is also used in Firefox when the Content-Type of an XHTML document is set to xmlish.
Node names will be preserved in __XML schema, so body or bOdY may appear.
Therefore, if XML is loaded from the server into an HTML document via the XMLHttpRequest__ technology, the node name will be preserved.
NodeName and __tagName__ are the same for elements.
But the nodeName attribute also exists in non-element nodes, and it has a special value in these nodes:
alert(document.nodeName) // #document
Most node types do not have a tagName attribute, and the tagName of annotation nodes in IE is !.
Therefore, nodeName is generally more meaningful than tagName. But tagName is like a simplified version, so you can use it when you are only dealing with element nodes.
innerHTML
innerHTML is part of the HTML5 standard, please see the link for details
It allows textual access to node content. The following example will output all the contents of document.body and replace it with the new content.
The paragraph
<script><br /> alert( document.body.innerHTML ) // read current contents<br /> Document.body.innerHTML = 'Yaaahooo!' // replace contents<br /> </script>
innerHTML will contain valid HTML. But browsers can also parse malformed HTML.
innerHTML can be used in any element node. It's very, very useful.
innerHTML pitFalls
innerHTML is not as simple as it looks. It has some traps that await newbies, and sometimes even experienced programmers cannot avoid them.
The innerHTML of the __table__ node in IE is read-only
In IE, innerHTML in COL, COLGROUP, FRAMESET, HEAD, HTML, STYLE, TABLE, TBODY, TFOOT, THEAD, TITLE, TR and other elements is read-only.
Except for TD, all innerHTML tags in the table tag in IE are read-only.
innerHTML cannot be appended
Judging from the composition of the statement, innerHTML can perform append operations, such as:
chatDiv.innerHTML = "

chatDiv.innerHTML = "How you doing?"
But what actually happened:
1. Old content is cleared
2. The new content is parsed and inserted. The content is not appended, it is regenerated.
Therefore, all pictures and other resources will be reloaded after the = operation, including smile.gif.
Fortunately, there are other ways to update content that do not use innerHTML and therefore do not have the problems mentioned above.
nodeValue
innerHTML is only valid for element nodes.
For other types of nodes, they use the nodeValue attribute to obtain content. The following example shows how it works on text nodes and comment nodes.
The text
<script><br /> for(var i=0; i<document.body.childNodes.length; i ) {<br /> alert(document.body.childNodes[i].nodeValue)<br /> }<br /> </script>
위 예에서는 빈 노드로 인해 일부 경고가 비어 있습니다. SCRIPT 노드의 경우 nodeValue === null입니다. SCRIPT가 요소 노드이기 때문입니다. 요소 노드의 경우 innerHTML을 사용합니다.
요약
노드 유형
노드 유형. 가장 중요한 것은 요소 노드가 1이고 텍스트 노드가 3이며 읽기 전용이라는 것입니다.
노드이름/태그이름
라벨 이름은 대문자입니다. 요소가 아닌 노드의 경우 nodeName에는 읽기 전용인 특수 값도 있습니다.
내부HTML
요소 노드의 내용, 쓰기 가능.
노드값
쓰기 가능한 텍스트 노드의 콘텐츠입니다.
DOM 노드에는 유형에 따라 다른 속성이 있습니다. 예를 들어 INPUT 태그에는 value 및 __checked__ 속성이 있습니다. 속성에는 href 등이 있습니다.
위 내용은 이 글의 전체 내용입니다. 모두 마음에 드셨으면 좋겠습니다.

JavaScript core data types are consistent in browsers and Node.js, but are handled differently from the extra types. 1) The global object is window in the browser and global in Node.js. 2) Node.js' unique Buffer object, used to process binary data. 3) There are also differences in performance and time processing, and the code needs to be adjusted according to the environment.

JavaScriptusestwotypesofcomments:single-line(//)andmulti-line(//).1)Use//forquicknotesorsingle-lineexplanations.2)Use//forlongerexplanationsorcommentingoutblocksofcode.Commentsshouldexplainthe'why',notthe'what',andbeplacedabovetherelevantcodeforclari

The main difference between Python and JavaScript is the type system and application scenarios. 1. Python uses dynamic types, suitable for scientific computing and data analysis. 2. JavaScript adopts weak types and is widely used in front-end and full-stack development. The two have their own advantages in asynchronous programming and performance optimization, and should be decided according to project requirements when choosing.

Whether to choose Python or JavaScript depends on the project type: 1) Choose Python for data science and automation tasks; 2) Choose JavaScript for front-end and full-stack development. Python is favored for its powerful library in data processing and automation, while JavaScript is indispensable for its advantages in web interaction and full-stack development.

Python and JavaScript each have their own advantages, and the choice depends on project needs and personal preferences. 1. Python is easy to learn, with concise syntax, suitable for data science and back-end development, but has a slow execution speed. 2. JavaScript is everywhere in front-end development and has strong asynchronous programming capabilities. Node.js makes it suitable for full-stack development, but the syntax may be complex and error-prone.

JavaScriptisnotbuiltonCorC ;it'saninterpretedlanguagethatrunsonenginesoftenwritteninC .1)JavaScriptwasdesignedasalightweight,interpretedlanguageforwebbrowsers.2)EnginesevolvedfromsimpleinterpreterstoJITcompilers,typicallyinC ,improvingperformance.

JavaScript can be used for front-end and back-end development. The front-end enhances the user experience through DOM operations, and the back-end handles server tasks through Node.js. 1. Front-end example: Change the content of the web page text. 2. Backend example: Create a Node.js server.

Choosing Python or JavaScript should be based on career development, learning curve and ecosystem: 1) Career development: Python is suitable for data science and back-end development, while JavaScript is suitable for front-end and full-stack development. 2) Learning curve: Python syntax is concise and suitable for beginners; JavaScript syntax is flexible. 3) Ecosystem: Python has rich scientific computing libraries, and JavaScript has a powerful front-end framework.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

SublimeText3 English version
Recommended: Win version, supports code prompts!

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

Dreamweaver Mac version
Visual web development tools

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools
