On Oct 19, 2009, at 3:19 PM, Peter Kasting wrote:
On Mon, Oct 19, 2009 at 1:10 PM, David Hyatt <hy...@apple.com> wrote:
I can get how editing in text fields you might feel a desire to
match the platform (where ragged selection may be the convention),
but once you get into rich text selection (images, floats, tables,
columns, etc.), there really is no platform precedent. Other
browsers just kind of lazily include a few more objects like images
and call it a day. We tried to do better than that.
I've actually been super frustrated with WebKit's selection behavior
for a long time, precisely because it tries to let you select
everything. In Firefox, in most cases* you just select the text out
of a page, which is pretty much always what I want. In Chrome I
find that I'm always managing to select an entire page or entire
table or various other things when I'm just trying to get the text
out of it. Darin (Fisher) has also complained to me about this in
the past
Concrete examples of where something weird happens would be helpful.
The gap code is obviously not perfect and so there's plenty of room
for improving it, which will help out Chrome on Mac users even if
Chrome on Windows goes to a different style of behavior.
dave
(hy...@apple.com)
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
