On Aug 20, 3:14 pm, Peter Kasting <pkast...@chromium.org> wrote:
> I chatted with several people just now about the Mac behavior, since unlike
> Linux, there aren't "blowing away my clipboard" concerns and it seemed to me
> that the argument above was compelling. According to pinkerton, the
> behavior in Chrome Mac is not just to match Safari, Camino, or platform
> conventions, but ultimately for the same reason that Camino decided to
> place-cursor-on-click instead of selecting all: editing was thought to be
> common enough that selecting all becomes frustrating.
>
> To me something is wrong when we argue opposite (non-platform-dependent)
> conclusions on different platforms, so I filedhttp://crbug.com/19879about
> collecting some real-world data to inform this debate. If we found that 99%
> of user navigations followed replacing all the text, for example, I would
> plead strongly with the Mac people to change their decision; if we found
> that 50% of navigations involved editing, I would probably argue we should
> reverse the Windows and Linux behaviors both.
To me that is the wrong approach. It should not be about "which way
do I guess the intent correctly most often" -- that way leads you to
MS Word-like guessing "what did the user _really_ mean?" and its
attendant frustrations. The intent should be instead to conform to
the principle of least surprise: what does the user expect when he
clicks on a text field? On OS X and Linux that is cursor placement,
not selection.
-Jonathan
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
