13605 2011-08-03 12:55:46 +0000 ES < and & escaping in inline script 2013-10-31 21:05:49 +0000 1 1 1 Unclassified HTML WG LC1 HTML/XHTML Compatibility Authoring Guide (ed: Eliot Graff) unspecified PC Linux RESOLVED FIXED P2 normal --- 1 plh eliotgra eliotgra mike public-html-admin public-html-wg-issue-tracking xn--mlform-iua public-html-bugzilla oldest_to_newest 52158 0 plh 2011-08-03 12:55:46 +0000 Polyglot indicates: [[ When polyglot markup must use script or style commands within its source code, it uses safe content. Safe content is content that does not contain a < or & character. The following example is safe because it does not contain problematic characters within the script tag. ]] Can one use \x3C and \x26 instead? If so, it would be nice to remind authors about them. 53158 1 mike 2011-08-04 05:07:10 +0000 mass-move component to LC1 53199 2 mike 2011-08-04 05:07:34 +0000 mass-move component to LC1 95633 3 eliotgra 2013-10-31 21:05:49 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted. CVS commit 1.2 Change Description: Added two sentences in section 3.6.2.1 The safe text content option: Polyglot markup is agnostic as to whether one uses a character entity or a numeric character reference, as long as it is valid. For polyglot markup, there is no difference between &amp; and &#x3C;. Thanks for the bug and your extreme patience.