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 11019 - The interface HTMLTableCellElement should provide a readonly attribute, that returns a NodeList of th elements which have been assigned to a cell via the "algorithm for assigning header cells". Similarly, the interface HTMLTableHeaderCellElement should ha
Summary: The interface HTMLTableCellElement should provide a readonly attribute, that ...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
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-10-13 09:23 UTC by contributor
Modified: 2011-08-04 05:00 UTC (History)
4 users (show)

See Also:


Attachments

Description contributor 2010-10-13 09:23:23 UTC
Section: http://www.whatwg.org/specs/web-apps/current-work/#attributes-common-to-td-and-th-elements

Comment:
The interface HTMLTableCellElement should provide a readonly attribute, that
returns a NodeList of th elements which have been assigned to a cell via the
"algorithm for assigning header cells". Similarly, the interface
HTMLTableHeaderCellElement should have an attribute returning all table cells
whose header cell it is.

Posted from: 141.99.252.30
Comment 1 Ian 'Hixie' Hickson 2010-10-13 10:46:20 UTC
What's the use case?
Comment 2 Ian 'Hixie' Hickson 2010-12-26 20:10:01 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 comment 1
Comment 3 Michael[tm] Smith 2011-08-04 05:00:16 UTC
mass-moved component to LC1