HTML characters are parsed (why?)
See original GitHub issueHi there,
Is it possible that react compiler turns html characters (like <
) inside a React code into literal characters, when compiled, causing problems when opened in a browser.
Is there a way to fix it?
Issue Analytics
- State:
- Created 10 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
HTML Entity Parser - GeeksforGeeks
HTML entity parser is the parser that takes HTML code as input and replaces all the entities of the special characters by the...
Read more >How to use / parse HTML entities and Unicode characters in a ...
How to use / parse HTML entities and Unicode characters in a JavaScript string · 1. HTML entities are syntax for the HTML...
Read more >8.2 Parsing HTML documents — HTML5 - W3C
This specification defines the parsing rules for HTML documents, whether they are syntactically correct or not. Certain points in the parsing algorithm are...
Read more >13.2 Parsing HTML documents - HTML Standard - WhatWG
When the HTML parser is decoding an input byte stream, it uses a character encoding and a confidence . The confidence is either...
Read more >HTML entities for special characters in plain text fields are not ...
Why are special characters encoded as HTML entities appearing as the source, such as &? ... Issue: Special characters are being seen in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@onion-soup Ah, it’s also worth knowing that you can do
<script charset="utf-8">
, if you’re unable to useutf-8
as document charset.PS. Correct is
<meta charset="utf-8">
, also unless you’re using XHTML you should (technically) not be using the self-closing slash.Yes, the issue was that my browser somehow set the encoding to ‘ISO’. I believe forcing the encoding with
<meta charset="utf8"../>
will solve the issue. Thanks!