Intended audience: users, XHTML/HTML coders (using editors or scripting), script developers (PHP, JSP, etc.), CSS coders, Web project managers, and anyone who wants to know how HTML escapes work in current browsers.
These tests check whether user agents handle character escapes as expected for HTML documents.
Note that the snapshot summaries of these test results are for released versions of the browsers tested. Versions that are still in development may provide better support for these features. The tests themselves do not test any vendor prefixes.
To see the test, click on the link in the left-most column. To see detailed results for a single test, click on the link in the right-most column. To submit test data for a single test, click on the link in the right-most column and then follow the link on that page.
The tables show the latest results from the W3C Test Framework. Below the tables are summaries of the results at a given date. The table data may be more up-to-date than the summary. The tables may also contain some incorrectly scored tests, and tests that relate to non-released versions of browsers. These are not included in the summary.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| hex ncr | A hexadecimal numeric character reference produces the intended character. | escapes-001 | ||||
| decimal ncr | A decimal numeric character reference produces the intended character. | escapes-002 | ||||
| lower-case entity | A lower case character entity reference produces the intended character. | escapes-003 | ||||
| upper-case entity | An upper case character entity reference produces the intended character. | escapes-004 | ||||
| supplementary character | A hexadecimal numeric reference containing the Unicode code point of a supplementary character produces the intended character. | escapes-005 |
Links: Section 8.1.4 • Latest results for section 8.1.4 • Submit data for section 8.1.4 • Related tests
All user agents produced characters as expected in the basic tests.
| Assertion | Gecko | Presto | Trident | WebKit | Detailed results | |
|---|---|---|---|---|---|---|
| hex ncr outside range of charset | An hexadecimal numeric reference containing the Unicode code point of a character which is not supported by the current character encoding still produces the intended character. | escapes-006 | ||||
| decimal ncr outside range of charset | A decimal numeric reference containing the Unicode code point of a character which is not supported by the current character encoding still produces the intended character. | escapes-007 | ||||
| character entity outside range of charset | A character entity reference for a Unicode code point which is not supported by the current character encoding still produces the intended character. | escapes-008 | ||||
| hex ncr for C1 position of euro sign | A hexadecimal numeric reference containing the code point for the euro in the Windows 1252 code page should produce a euro sign. | escapes-009 | ||||
| decimal ncr for C1 position of euro sign | A decimal numeric reference containing the code point for the euro in the Windows 1252 code page should produce a euro sign. | escapes-010 |
Links: Section 8.1.4 • Latest results for section 8.1.4 • Submit data for section 8.1.4 • Related tests
All user agents correctly displayed characters that were not in the encoding of the page.
All user agents displayed the euro sign in HTML if the escape used the Windows 1252 code point number rather than the correct Unicode code point number.