[Bug 24645] New: li should provide DOM interface to its rendered value representation

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24645

            Bug ID: 24645
           Summary: li should provide DOM interface to its rendered value
                    representation
           Product: WHATWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTML
          Assignee: ian@hixie.ch
          Reporter: silviapfeiffer1@gmail.com
        QA Contact: contributor@whatwg.org
                CC: mike@w3.org, public-html-admin@w3.org,
                    public-html-wg-issue-tracking@w3.org, w3c@mjec.net
        Depends on: 24644

+++ This bug was initially created as a clone of Bug #24644 +++

<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 on the CC list for the bug.

Received on Thursday, 13 February 2014 07:16:04 UTC