Can you retrieve the value from an attribute as it appeared in the source?
Commenting on this question made me wonder.
In JavaScript, is it possible to get the "raw" value of a HTML attribute, i.e. the way it was written in the source before parsing?
Say you have this HTML:
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title);
</script>
What do I need to write in the script to make it output the original escaped value of the title, rather than the parsed one?
JavaScript nodes have a lot of properties and values, but in this case, none that say "The section"
instead of "The section"
.
javascript html dom
add a comment |
Commenting on this question made me wonder.
In JavaScript, is it possible to get the "raw" value of a HTML attribute, i.e. the way it was written in the source before parsing?
Say you have this HTML:
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title);
</script>
What do I need to write in the script to make it output the original escaped value of the title, rather than the parsed one?
JavaScript nodes have a lot of properties and values, but in this case, none that say "The section"
instead of "The section"
.
javascript html dom
1
That could only be done using String parsing on the HTML you get via an asynchronous GET request. Obviously the DOM API cannot access elements not in the DOM, and as soon as an element is in the DOM, it has obviously been parsed.
– connexo
Nov 22 '18 at 20:30
Ah yes, I don't want to to that. At best, downloading the same HTML file again and having to search through it; at worst, re-invoking the web app, with who knows what side effects. No, no.
– Mr Lister
Nov 22 '18 at 20:46
add a comment |
Commenting on this question made me wonder.
In JavaScript, is it possible to get the "raw" value of a HTML attribute, i.e. the way it was written in the source before parsing?
Say you have this HTML:
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title);
</script>
What do I need to write in the script to make it output the original escaped value of the title, rather than the parsed one?
JavaScript nodes have a lot of properties and values, but in this case, none that say "The section"
instead of "The section"
.
javascript html dom
Commenting on this question made me wonder.
In JavaScript, is it possible to get the "raw" value of a HTML attribute, i.e. the way it was written in the source before parsing?
Say you have this HTML:
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title);
</script>
What do I need to write in the script to make it output the original escaped value of the title, rather than the parsed one?
JavaScript nodes have a lot of properties and values, but in this case, none that say "The section"
instead of "The section"
.
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title);
</script>
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title);
</script>
javascript html dom
javascript html dom
edited Nov 22 '18 at 21:01
Mr Lister
asked Nov 22 '18 at 20:18
Mr ListerMr Lister
35.1k1076121
35.1k1076121
1
That could only be done using String parsing on the HTML you get via an asynchronous GET request. Obviously the DOM API cannot access elements not in the DOM, and as soon as an element is in the DOM, it has obviously been parsed.
– connexo
Nov 22 '18 at 20:30
Ah yes, I don't want to to that. At best, downloading the same HTML file again and having to search through it; at worst, re-invoking the web app, with who knows what side effects. No, no.
– Mr Lister
Nov 22 '18 at 20:46
add a comment |
1
That could only be done using String parsing on the HTML you get via an asynchronous GET request. Obviously the DOM API cannot access elements not in the DOM, and as soon as an element is in the DOM, it has obviously been parsed.
– connexo
Nov 22 '18 at 20:30
Ah yes, I don't want to to that. At best, downloading the same HTML file again and having to search through it; at worst, re-invoking the web app, with who knows what side effects. No, no.
– Mr Lister
Nov 22 '18 at 20:46
1
1
That could only be done using String parsing on the HTML you get via an asynchronous GET request. Obviously the DOM API cannot access elements not in the DOM, and as soon as an element is in the DOM, it has obviously been parsed.
– connexo
Nov 22 '18 at 20:30
That could only be done using String parsing on the HTML you get via an asynchronous GET request. Obviously the DOM API cannot access elements not in the DOM, and as soon as an element is in the DOM, it has obviously been parsed.
– connexo
Nov 22 '18 at 20:30
Ah yes, I don't want to to that. At best, downloading the same HTML file again and having to search through it; at worst, re-invoking the web app, with who knows what side effects. No, no.
– Mr Lister
Nov 22 '18 at 20:46
Ah yes, I don't want to to that. At best, downloading the same HTML file again and having to search through it; at worst, re-invoking the web app, with who knows what side effects. No, no.
– Mr Lister
Nov 22 '18 at 20:46
add a comment |
1 Answer
1
active
oldest
votes
There is no way to get parsed Unicode charachter in the browser like source
HTML file and as
is a space then we can use this workaround for any title has space between its words.
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title.split(' ').join(' '));
</script>
I know it is silly answer,
but if really intended to process space unicode then hit the url which has this <section id="theSection" title="The section">The section</section>
with fetch(url)
like below:
fetch('stackoverflow.com')
.then(async (res) => {
const text = await res.text();
// process the text with any unicode charachter as it is now 100% string
}
);
Now the source HTML file is a string. It is better to use in your case javascript on string with a regex to find what do you want to process in html source.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437564%2fcan-you-retrieve-the-value-from-an-attribute-as-it-appeared-in-the-source%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no way to get parsed Unicode charachter in the browser like source
HTML file and as
is a space then we can use this workaround for any title has space between its words.
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title.split(' ').join(' '));
</script>
I know it is silly answer,
but if really intended to process space unicode then hit the url which has this <section id="theSection" title="The section">The section</section>
with fetch(url)
like below:
fetch('stackoverflow.com')
.then(async (res) => {
const text = await res.text();
// process the text with any unicode charachter as it is now 100% string
}
);
Now the source HTML file is a string. It is better to use in your case javascript on string with a regex to find what do you want to process in html source.
add a comment |
There is no way to get parsed Unicode charachter in the browser like source
HTML file and as
is a space then we can use this workaround for any title has space between its words.
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title.split(' ').join(' '));
</script>
I know it is silly answer,
but if really intended to process space unicode then hit the url which has this <section id="theSection" title="The section">The section</section>
with fetch(url)
like below:
fetch('stackoverflow.com')
.then(async (res) => {
const text = await res.text();
// process the text with any unicode charachter as it is now 100% string
}
);
Now the source HTML file is a string. It is better to use in your case javascript on string with a regex to find what do you want to process in html source.
add a comment |
There is no way to get parsed Unicode charachter in the browser like source
HTML file and as
is a space then we can use this workaround for any title has space between its words.
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title.split(' ').join(' '));
</script>
I know it is silly answer,
but if really intended to process space unicode then hit the url which has this <section id="theSection" title="The section">The section</section>
with fetch(url)
like below:
fetch('stackoverflow.com')
.then(async (res) => {
const text = await res.text();
// process the text with any unicode charachter as it is now 100% string
}
);
Now the source HTML file is a string. It is better to use in your case javascript on string with a regex to find what do you want to process in html source.
There is no way to get parsed Unicode charachter in the browser like source
HTML file and as
is a space then we can use this workaround for any title has space between its words.
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title.split(' ').join(' '));
</script>
I know it is silly answer,
but if really intended to process space unicode then hit the url which has this <section id="theSection" title="The section">The section</section>
with fetch(url)
like below:
fetch('stackoverflow.com')
.then(async (res) => {
const text = await res.text();
// process the text with any unicode charachter as it is now 100% string
}
);
Now the source HTML file is a string. It is better to use in your case javascript on string with a regex to find what do you want to process in html source.
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title.split(' ').join(' '));
</script>
<section id="theSection" title="The section">The section</section>
<script>
console.log(document.getElementById('theSection').title.split(' ').join(' '));
</script>
answered Nov 22 '18 at 21:32
PoodePoode
36337
36337
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437564%2fcan-you-retrieve-the-value-from-an-attribute-as-it-appeared-in-the-source%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
That could only be done using String parsing on the HTML you get via an asynchronous GET request. Obviously the DOM API cannot access elements not in the DOM, and as soon as an element is in the DOM, it has obviously been parsed.
– connexo
Nov 22 '18 at 20:30
Ah yes, I don't want to to that. At best, downloading the same HTML file again and having to search through it; at worst, re-invoking the web app, with who knows what side effects. No, no.
– Mr Lister
Nov 22 '18 at 20:46