[Selection API] Plans regarding multiple ranges?

• From: Joanmarie Diggs <jdiggs@igalia.com>
• Date: Wed, 12 Nov 2014 15:15:02 -0500
• To: "public-webapps@w3.org" <public-webapps@w3.org>
• CC: W3C WAI Protocols & Formats <public-pfwg@w3.org>
• Message-ID: <5463BFC6.4090101@igalia.com>

Hi all.

The current draft of the Selection API states:

    This specification follows non-Gecko engines in restricting
    selections to at most one range, but the API was still originally
    designed for selections with arbitrary numbers of ranges. This
    explains oddities like the coexistence of removeRange() and
    removeAllRanges(), and a getRangeAt() method that takes an integer
    argument that must always be zero.

If things change and multiple ranges are supported, there may (or may
not) be associated accessibility needs to address or techniques to
create. If multiple ranges are not supported, then there are clearly not
such needs or techniques. So before we (PFWG) give it more thought, do
you happen to know what your plans are for multiple ranges? In
particular, if some non-Gecko engine added support for multiple ranges,
would your API change to reflect that? Or are the corner cases just too
unpleasant?

Thanks in advance. Take care.
--joanie

Received on Wednesday, 12 November 2014 20:15:44 UTC