This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Is it intentional that text in a MathML text integration point doesn't ignore U+0000 and doesn't reconstruct the active formatting elements?
It seems like it works exactly like text in <span>, no?
(In reply to comment #2) > It seems like it works exactly like text in <span>, no? No. Text in a span reconstructs the active formatting elements and ignores U+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 Change Description: see diff given below Rationale: Oh, wow, yeah, I totally missed a case there.
Checked in as WHATWG revision r6226. Check-in comment: Change how U+0000 NULLs are parsed in MathML text integration points; may also have some side-effects on misnested formatting elements. http://html5.org/tools/web-apps-tracker?from=6225&to=6226
mass-moved component to LC1