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 16946 - Self-Closing Input should be acknowledged for <input> in Tree Construction "In Table" Insertion Mode
Summary: Self-Closing Input should be acknowledged for <input> in Tree Construction "I...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-05 21:07 UTC by Raj Doshi
Modified: 2012-10-14 21:48 UTC (History)
5 users (show)

See Also:

Attachments

Description Raj Doshi 2012-05-05 21:07:58 UTC 
In the Tree Construction "In Table" insertion mode (section 8.2.5.4.9), there is a condition for "input" start tags.  Just like the "In Body" input case, I believe it should say "Acknowledge the token's self-closing flag, if it is set."  Currently, this is omitted under the "Otherwise" case, so using <input/> in that case results in an additional error.  The hidden case should be fine without that because it ultimately uses the "In Body" behavior.
Comment 1 contributor 2012-07-18 07:03:47 UTC 
This bug was cloned to create bug 17852 as part of operation convergence.
Comment 2 Edward O'Connor 2012-09-21 23:54: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: Awaiting Additional Information
Change Description: No spec change.
Rationale: Did you test this in browsers? Table parsing is notoriously
strange; I think we should be wary of changing the spec here unless we
can establish there isn't much of a compat risk.
Comment 3 Silvia Pfeiffer 2012-10-07 06:07:32 UTC 
Would it be ok to apply the patche from WHATWG for this, see bug 17852?
https://github.com/w3c/html/commit/09a97eb1269e25332294fc4d205327c320b21ba4
Comment 4 Edward O'Connor 2012-10-14 15:53:49 UTC 
Yes, r7417 and r7418 look reasonable to me.
Comment 5 Silvia Pfeiffer 2012-10-14 21:48:51 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-v2.html

Status: Accepted
Change Description:
https://github.com/w3c/html/commit/09a97eb1269e25332294fc4d205327c320b21ba4
https://github.com/w3c/html/commit/731d272363e726d3c1e7011e3fa38d2cf12bd769

Rationale: accepted WHATWG change