Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Users Search
Help Dashboard Sign In Sign Up
Q&A Code Reviews Meta
Q&A
Posts Tags Edits
Ask Question

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

36%
+2 −5
Q&A What problem does innerHTML solves?

I understand that innerHTML does all the following actions: It makes the element we work on (or even the entire DOM tree that we work on if that element is <body>) to be copy-pasted into a...

1 answer  ·  posted 3y ago by deleted user  ·  edited 3y ago by deleted user

Question javascript
#10: Post edited by (deleted user) · 2021-10-01T23:49:20Z (about 3 years ago)
  • I understand that `innerHTML` does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does at least one extra thing as defuncting JavaScript so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I understand that `innerHTML` does all the following actions:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does at least one extra thing as defuncting JavaScript so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
#9: Post edited by (deleted user) · 2021-10-01T23:40:54Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does at least one extra thing as defuncting JavaScript so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I understand that `innerHTML` does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does at least one extra thing as defuncting JavaScript so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
#8: Post edited by (deleted user) · 2021-10-01T23:38:13Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does some extra things so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does at least one extra thing as defuncting JavaScript so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
#7: Post edited by (deleted user) · 2021-10-01T23:20:10Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does some extra things so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does some extra things so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
#6: Post edited by (deleted user) · 2021-10-01T11:19:09Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: I assume that the original author meant "changing" not replacing (with the contents of another element), but `innerHTML` does some extra things so I would assume it's not a mere HTML editing solution
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: `innerHTML` does some extra things so I would assume it's not a mere value replacement
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
#5: Post edited by (deleted user) · 2021-10-01T07:07:28Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • * Replacing the contents of an element: Wouldn't that typically be done with `textContent` and/or `replaceChild()`?
  • * Appending HTML to an element: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • About the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML):
  • * _Replacing the contents of an element_: I assume that the original author meant "changing" not replacing (with the contents of another element), but `innerHTML` does some extra things so I would assume it's not a mere HTML editing solution
  • * _Appending HTML to an element_: I assume that this would typically be done with `insertAdjacentHTML()`?
#4: Post edited by (deleted user) · 2021-10-01T06:26:15Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way)?
  • * Replacing the contents of an element: Wouldn't that typically be done with `textContent` and/or `replaceChild()`?
  • * Appending HTML to an element: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way?)
  • * Replacing the contents of an element: Wouldn't that typically be done with `textContent` and/or `replaceChild()`?
  • * Appending HTML to an element: I assume that this would typically be done with `insertAdjacentHTML()`?
#3: Post edited by (deleted user) · 2021-10-01T06:23:46Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way)?
  • * Replacing the contents of an element: Wouldn't that typically be done with `textDocument()` and/or `replaceChild()`?
  • * Appending HTML to an element: I assume that this would typically be done with `insertAdjacentHTML()`?
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way)?
  • * Replacing the contents of an element: Wouldn't that typically be done with `textContent` and/or `replaceChild()`?
  • * Appending HTML to an element: I assume that this would typically be done with `insertAdjacentHTML()`?
#2: Post edited by (deleted user) · 2021-10-01T06:10:21Z (about 3 years ago)
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • If I had a mistake in understanding please tell me, but if not, I misunderstand what problem would this property solve? I could think about experimenting, if someone wants to experiment on a particular DOM tree, but just without any "JavaScript bias" of the original DOM tree, which may interfere such experimenting.
  • I find `innerHTML` property confusing; I understand that it does all the following actions together:
  • * It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
  • * The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
  • * Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document
  • What problem would this property solve that can't be done with other methods, besides perhaps emptying the current document (why doing that?) and outputting the full HTML of an element (is it really the only way)?
  • * Replacing the contents of an element: Wouldn't that typically be done with `textDocument()` and/or `replaceChild()`?
  • * Appending HTML to an element: I assume that this would typically be done with `insertAdjacentHTML()`?
#1: Initial revision by (deleted user) · 2021-10-01T05:22:57Z (about 3 years ago) 
What problem does innerHTML solves?
I find `innerHTML` property confusing; I understand that it does all the following actions together:

* It makes the element we work on (or even the entire DOM tree that we work on if that element is `<body>`) to be copy-pasted into a new empty document
* The new document to which the data was copied, naturally lacks any whatsoever JavaScript of the previous document
* Although the data was copied into a new document, the browser will present the HTML change as if it was done in the original document

If I had a mistake in understanding please tell me, but if not, I misunderstand what problem would this property solve? I could think about experimenting, if someone wants to experiment on a particular DOM tree, but just without any "JavaScript bias" of the original DOM tree, which may interfere such experimenting.
javascript