#58256 closed defect (bug) (fixed)
HTML API: Restore mistakenly-removed content in documentation.
| Reported by: | dmsnell | Owned by: | audrasjb |
|---|---|---|---|
| Priority: | normal | Milestone: | 6.3 |
| Component: | HTML API | Version: | 6.3 |
| Severity: | normal | Keywords: | has-patch commit |
| Cc: | Focuses: | docs |
Description
In a3ed152 the Unicode replacement character was mistakenly removed, being believed to be a text rendering mistake, because the character is the replacement character used in situations where those text mistakes occur.
However, the purpose of including the character was to communicate what it looks like and why the Tag Processor won't insert it into the document (which would be wrong from the Unicode point of view for such a streaming processor that doesn't produce the final rendered view of the text).
In this patch we're bringing back the character and adding a small clue to try and remove the confusion that previously led to its unwanted removal.
Change History (5)
This ticket was mentioned in PR #4426 on WordPress/wordpress-develop by @dmsnell.
3 years ago
#1
@audrasjb commented on PR #4426:
3 years ago
#5
Committed in https://core.trac.wordpress.org/changeset/55723
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Trac: #58256-ticket
In a3ed152c54c117d39d32a72a3d22f082dd5ffa7f the Unicode replacement character was mistakenly removed, being believed to be a text rendering mistake, because the character _is_ the replacement character used in situations where those text mistakes occur.
However, the purpose of including the character was to communicate what it looks like and why the Tag Processor won't insert it into the document (which would be wrong from the Unicode point of view for such a streaming processor that doesn't produce the final rendered view of the text).
In this patch we're bringing back the character and adding a small clue to try and remove the confusion that previously led to its unwanted removal.