- From: <bugzilla@jessica.w3.org>
- Date: Thu, 13 Feb 2014 06:26:13 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24644 Bug ID: 24644 Summary: li should provide DOM interface to its value representation Product: HTML WG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P2 Component: HTML5 spec Assignee: dave.null@w3.org Reporter: w3c@mjec.net QA Contact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html-admin@w3.org, public-html-wg-issue-tracking@w3.org (Apologies if this should have been filed against HTML.next) <li> children of <ol> (and less significantly <ul>) may have a list marker rendered next to them. For children of <ol> the value of this marker can be set explicitly with the value attribute. When the value is not set (including because it is not a child of <ol>) the user agent will automatically determine and render a marker, if applicable in accordance with the CSS rules applied to the element. The automatically determined (or rendered) value is not DOM-accessible. I propose that the DOM interface for li elements be expanded to include a new property: readonly attribute Node? renderedValue; This would return an Element or Text node, being the automatically calculated value for that li (or null if no list marker is rendered). In the alternative, this could be only available for li children of ol elements: readonly attribute long ordinalValue; being the ordinal value <http://www.w3.org/html/wg/drafts/html/master/grouping-content.html#ordinal-value> of the li element. My suggestion is that the value is readonly to simplify implementation. The most obvious use case for this property is cross-referencing in documents, for example where paragraphs are numbered. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 13 February 2014 06:26:52 UTC