This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
3.2.6 Requirements relating to bidirectional-algorithm formatting characters http://www.w3.org/TR/html5/content-models.html#requirements-relating-to-bidirectional-algorithm-formatting-characters There is one sentence that reads: -- However, the use of these characters is restricted so that any embedding or overrides generated by these characters do not start and end with different parent elements, and so that all such embeddings and overrides are explicitly terminated by a U+202C POP DIRECTIONAL FORMATTING character. -- Shouldn't there be an explicit statement such as "any end tag for a run of phrasing content must be treated as if a U+202C had been inserted at that point" (filing some issues that were overlooked in I18N tracker)
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: Rejected Change Description: none Rationale: The requirements described in this paragraph are authoring requirements, not UA requirements. Authors who use bidirectional-algorithm formatting characters manually must conform to those requirements but we can't have authors process end tags in any specific manner — that would be UA behaviour.