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 11166 - <svg><foreignObject><div><frameset> and s/frameset/select/ can cause the insertion mode to be reset with <frameset> and <select> at the top of the stack, so these are no longer fragment-case-only
Summary: <svg><foreignObject><div><frameset> and s/frameset/select/ can cause the inse...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P1 critical
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
: 11167 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-10-29 11:37 UTC by contributor
Modified: 2011-08-04 05:01 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-10-29 11:37:00 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-insertion-mode

Comment:
<svg><foreignObject><div><frameset> and s/frameset/select/ can cause the
insertion mode to be reset with <frameset> and <select> at the top of the
stack, so these are no longer fragment-case-only

Posted from: 88.131.66.80
Comment 1 James Graham 2010-10-29 11:45:20 UTC 
*** Bug 11167 has been marked as a duplicate of this bug. ***
Comment 2 Ian 'Hixie' Hickson 2010-12-27 23:44:55 UTC 
Does this have any implications beyond the editorial? I can't think of any off-hand, but I'll check when I make the edit if nobody else has thought of any by then.
Comment 3 Ian 'Hixie' Hickson 2011-01-12 20:10:19 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: Rejected
Change Description: no spec change
Rationale: Actually, this is wrong. The reset algorithm doesn't get called for those two cases, as far as I can tell. If I'm wrong, please walk me through the steps that get the reset algorithm called with either <frameset> or <select> as the current node.
Comment 4 Michael[tm] Smith 2011-08-04 05:01:47 UTC 
mass-moved component to LC1