Reserved HTML characters "<" and ">" used in FAQs
See original GitHub issueWhere to find the issue
FAQs
Describe the issue
There is a lot of incorrect literal usage of the characters <
and >
in the FAQs. These are characters reserved to delimit HTML tags.
These are used in:
- Mathematical comparisons, such as
>= 63dB
- In a sequence of instructions, such as
'Settings' -> 'Reset App'
and'Security & Location' > 'Location' > 'App level permissions'
Suggestion
Replace literal usage of the reserved characters <
and >
in the FAQs by their escaped equivalents as follows
Character | Escaped character |
---|---|
< |
< |
> |
> |
References
Internal Tracking ID: EXPOSUREAPP-14343
Issue Analytics
- State:
- Created 10 months ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to use the HTML reserved character ? - GeeksforGeeks
The way we can use HTML reserved characters is using an HTML entity so that reserved characters are not interpreted as HTML code....
Read more >HTML Entities - W3Schools
Character entities are used to display reserved characters in HTML. A character entity looks like this: &entity_name;. OR. &#entity_number;. To display a less ......
Read more >Guide to: Using HTML Tags/Characters in Labels
In HTML, there are some characters that are considered reserved (such as less than (<) and greater than (>) signs, which also signify...
Read more >Use HTML Entities to Display Reserved Characters #tryminim
Browsers will always read certain characters as being intended for use in HTML code.An example is the angled brackets that we use to...
Read more >What Are The Reserved Characters In (X)HTML?
Yes, I've googled it, and surprisingly got confusing answers. One page says that < > & " are the only reserved characters 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 FreeTop 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
Top GitHub Comments
@larswmh
I’m happy to prepare a PR for the changes.
Since both the above PRs have been merged, this issue is now resolved.