On Tue, Jun 28, 2011 at 1:38 PM, Aryeh Gregor simetrical+...@gmail.com wrote:
I've updated the spec to require this:
https://bitbucket.org/ms2ger/dom-range/changeset/b9ca1640aeee
http://html5.org/specs/dom-range.html#apis-for-the-browsing-context-selection:-the-selection-interface
The
On Fri, Jun 17, 2011 at 1:40 PM, Aryeh Gregor aryehgre...@gmail.com wrote:
However, I'd still like to normalize author-set selections somewhat.
At a minimum, for instance, we could guarantee that a selection's
boundary point is always in a Text or Element node that descends from
a Document.
On Fri, Jun 17, 2011 at 4:33 AM, Ojan Vafai o...@chromium.org wrote:
On Thu, Jun 16, 2011 at 12:09 PM, Ryosuke Niwa rn...@webkit.org wrote:
Yes, I think all selection modified by user should be normalized by
default.
I'm talking more about programmatically set selection. I think we'll
On Thu, Jun 16, 2011 at 12:33 PM, Ojan Vafai o...@chromium.org wrote:
On Thu, Jun 16, 2011 at 12:09 PM, Ryosuke Niwa rn...@webkit.org wrote:
Yes, I think all selection modified by user should be normalized by
default.
I'm talking more about programmatically set selection. I think we'll
On 6/17/11 1:40 PM, Aryeh Gregor wrote:
At a minimum, for instance, we could guarantee that a selection's
boundary point is always in a Text or Element node that descends from
a Document. That would be a big simplification by itself. Does
anyone object to that?
At first blush, that seems
Since I've somehow managed to send from the wrong address again for
the third time in 48 hours, here's yet another resent mail, probably
to be followed by a fourth when I respond to Boris' response and Gmail
auto-selects my non-list address again for the from address instead of
my list address:
Another bounce, resending again. Sorry for duplicate mail to the
non-list recipients.
On Wed, Jun 15, 2011 at 5:46 PM, Ryosuke Niwa rn...@webkit.org wrote:
WebKit's current behavior makes impossible to set selection inside an empty
span (See http://webkit.org/b/15256) so we're planning to
On 6/16/11 3:00 PM, Aryeh Gregor wrote:
Assuming we don't match WebKit/Opera here, though, does everyone agree
we should still place constraints on what selections can be generated
by *user* actions? E.g., if you havebfoo/bbar, and the user
places the cursor in between foo and bar by any means,
On Thu, Jun 16, 2011 at 11:50 AM, Aryeh Gregor aryehgre...@gmail.comwrote:
For instance, could we just say that empty inline
elements can have the cursor inside them, so foo{}b/bbar and
foob/b{}bar both normalize to foob{}/bbar? That would solve
the specific bug.
What if we had
On Thu, Jun 16, 2011 at 12:12 PM, Boris Zbarsky bzbar...@mit.edu wrote:
This is an interesting situation which is the inverse of the bidi problem.
In the bidi case there is a single point in the DOM which corresponds to
two different user-perceived selection positions. In this case, a single
On Thu, Jun 16, 2011 at 12:12 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 6/16/11 3:00 PM, Aryeh Gregor wrote:
Assuming we don't match WebKit/Opera here, though, does everyone agree
we should still place constraints on what selections can be generated
by *user* actions? E.g., if you
On Thu, Jun 16, 2011 at 12:09 PM, Ryosuke Niwa rn...@webkit.org wrote:
On Thu, Jun 16, 2011 at 11:50 AM, Aryeh Gregor aryehgre...@gmail.com
wrote:
Assuming we don't match WebKit/Opera here, though, does everyone agree
we should still place constraints on what selections can be generated
by
On 6/16/11 3:22 PM, Ryosuke Niwa wrote:
It's inevitable in some sense because we can't guess the user intent
although Firefox and Microsoft Word seem to use the direction to which
user moved caret as a hint.
Indeed.
And the fact that the two DOM positions correspond to the same
user-visible
On Wed, Jun 15, 2011 at 2:39 PM, Aryeh Gregor aryehgre...@gmail.com wrote:
I originally thought the WebKit/Opera behavior was unreasonable, but
I've come around to thinking it makes more sense than IE/Gecko. It's
simpler and more consistent. If selections are always normalized, we
can
I sent this to the list from the wrong address and it bounced, so I'm
resending it from the right address. You should probably read it
before you read Ryosuke's reply, which wound up getting to the list
first because he was CC'd and got my message despite it bouncing from
the list.
There
15 matches
Mail list logo
