On Thu, Aug 20, 2009 at 12:07 PM, JT  Olds<jto...@xnet5.com> wrote:
>
> So, history of this discussion:
> http://code.google.com/p/chromium/issues/detail?id=19508
> http://code.google.com/p/chromium/issues/detail?id=19648#c15
>
> Basically, I feel that if the attempt is to make Chromium feel like a
> native application on all operating systems, the standards of that
> operating system should be followed.
>
> Specifically, the omnibox does not follow conventional Linux
> highlighting standards. To wit,
> 1) on a single click to the omnibox, the cursor should be placed. The
> contents of the omnibox should not be selected. Perhaps there can be a
> button that selects the contents nearby in the UI? I don't mind if ^L
> selects the contents.
> 2) On a double click, a word in the omnibox should be selected. I
> actually wouldn't mind too much if the convention here was altered
> ever so slightly and a double click selected the entire box contents.
> 3) On a triple click, if a word was selected on double click, the
> entire contents should be selected.
> 4) Any time content in the box is selected, it should be in the
> PRIMARY buffer.

A lot of webpages highlight stuff without your input (with
javascript). Are you sure you want a webpage to be able to clobber
your clipboard?

>
> Now, Evan pointed out at comment 15 of Issue 19648 that Firefox does
> not even comply with point 4. I was unaware of this, but I'm fairly
> sure that explains my frequent confusion about when my copy/paste and
> selection buffers are not the data or URL I think they should be. Just
> because Firefox is broken here doesn't mean Chromium should be too.
>
> Please make Chromium follow Linux conventions.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to