This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html Multipage: http://www.whatwg.org/C#user-agent-conformance-criteria Complete: http://www.whatwg.org/c#user-agent-conformance-criteria Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: After reading the Authoring Conformance Criteria for bidirectional-algorithm formatting characters, I was expecting there to be explicit guidance for how user-agents should handle documents that do not meet the authoring conformance criteria. I assume user agents should quietly insert enough POP DIRECTIONAL FORMATTING characters to reset whatever bidi formatting characters are present, but it would be nice to have that spelled out. Posted from: 202.7.241.231 User agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 Iceweasel/30.0a2
It's in the CSS spec. The section "Requirements relating to the bidirectional algorithm", subsection "User agent conformance criteria", says that the CSS rules regarding bidi are normative, even on UAs that don't support CSS per se.
I'm not sure how to improve this. The two sections are right next to each other.