This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8966 - Consider "<svg><desc><div><svg><desc><b>X" — Should we change "Pop elements from the stack of open elements until the current node is in the HTML namespace." in the in-foreign-content mode to actually be "Pop elements until there's no element in scope t
Summary: Consider "<svg><desc><div><svg><desc><b>X" — Should we change "Pop elements f...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P1 critical
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on: 8767
Blocks:
  Show dependency tree / graph
 
Reported: 2010-02-13 10:26 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-02-13 10:26:32 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#parsing-main-inforeign

Comment:
Consider "<svg><desc><div><svg><desc><b>X" — Should we change "Pop elements
from the stack of open elements until the current node is in the HTML
namespace." in the in-foreign-content mode to actually be "Pop elements until
there's no element in scope that's from any namespace other than the HTML
namespace" or some such?

Posted from: 98.248.33.53 by ian@hixie.ch
Comment 1 Simon Pieters 2010-02-15 22:07:14 UTC 
You mean <svg><desc><div><svg><b>X, right?

I think no. The popping is only for compat. Popping all the way would be unnecessarily draconian for minor mistakes when using e.g. MathML in SVG.

OTOH, for <svg><desc><svg><b>X, we do pop all the way. Maybe instead we should pop until an <svg> or <math> has been popped.
Comment 2 Ian 'Hixie' Hickson 2010-02-18 08:08:55 UTC 
Delaying this until after bug 8767 is fixed.
Comment 3 Ian 'Hixie' Hickson 2010-02-25 02:29:02 UTC 
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: Partially Accepted
Change Description: see diff given below
Rationale: Concurred with comment 1.
Comment 4 Simon Pieters 2010-07-21 11:30:33 UTC 
It seems this fix was not quite right for e.g.

<math><annotation-xml><svg><u>

or 

<svg><svg><u>

I guess we need to either revert this or come up with something that works better.
Comment 5 Ian 'Hixie' Hickson 2010-08-16 21:01:35 UTC 
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: Partially Accepted
Change Description: see diff given below
Rationale: I figured out a better (I hope!) solution.