W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2011

[whatwg] Request for implementer feedback: granularity definitions for Selection.modify()

From: Aryeh Gregor <Simetrical+w3c@gmail.com>
Date: Sun, 30 Jan 2011 16:33:49 -0500
Message-ID: <AANLkTi=QY2WaSTLR0HuTYjBEyk-2ZTcXGsXP-D-oOLhq@mail.gmail.com>
I'm working on a definition of Selection.modify(), and have run into
the problem of how to define the various granularities used there.
(See <https://developer.mozilla.org/en/DOM/selection/modify> for basic
docs.)  The intent of the API is clearly that, e.g.,
selection.modify("move", "right", "character") should do something
like hitting the right arrow key, selection.modify("extend", "right",
"line") should be like Shift+Down, etc.  But this is platform-specific
in practice -- e.g., Ctrl+Left and Ctrl+Right use different
definitions of word boundaries in different programs I use.

To what degree should I try to define how these granularities work?  I
could go ahead and say that moving by characters should be done by
moving to the next grapheme cluster boundary as defined by UAX#29, for
example.  Or I could say that it should follow platform conventions
for when the user advances by a character, e.g., using the right and
left arrow keys.  Or maybe something else?  What would implementers
prefer?

In practice, in other places where this stuff is needed (like
line-breaking or :first-letter), we just leave it entirely undefined,
which doesn't seem ideal but perhaps isn't fully avoidable.
Received on Sunday, 30 January 2011 13:33:49 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:30 UTC