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 10204 - The algorithm is unclear here whether we mean the "current node" at this point in time or the "current node" at the time the insertion occurs (which might be different). As an example, consider "<table><p><p>Foo". I think you mean the current element at
Summary: The algorithm is unclear here whether we mean the "current node" at this poin...
Status: RESOLVED NEEDSINFO
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: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-19 22:07 UTC by contributor
Modified: 2010-10-04 14:32 UTC (History)
6 users (show)

See Also:


Attachments

Description contributor 2010-07-19 22:07:46 UTC
Section: http://www.whatwg.org/specs/web-apps/current-work/#parsing-main-intable

Comment:
The algorithm is unclear here whether we mean the "current node" at this point
in time or the "current node" at the time the insertion occurs (which might be
different).  As an example, consider "<table><p><p>Foo".  I think you mean the
current element at the time of insertion.

Posted from: 98.210.108.185
Comment 1 Adam Barth 2010-07-19 22:08:34 UTC
Not really a critical issue, but Ian ask me to file parser bugs as P1/critical.
Comment 2 Ian 'Hixie' Hickson 2010-08-16 18:13:33 UTC
Adam: It is unclear to me which algorithm you mean. Could you elaborate?
Comment 3 Ian 'Hixie' Hickson 2010-08-16 21:20:30 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: Did Not Understand Request
Change Description: no spec change
Rationale: See above.