Linux: Fix two issues of omnibox.

BUG=23107
Last character of completed path in Omnibar is the wrong color after inline autocomplete
BUG=24818
Funky behavior in omnibar editing
TEST=Run chromium with a clean profile, then access go/go (or similar url) for several times to make sure inputting 'g' can trigger inline autocomplete. Then input "go/go" and then check if the last char is gray.
TEST=Input something into omnibox to trigger inline autocomplete, then press ctrl-right and hold ctrl key, to move the cursor and clear the text selection, then release ctrl key, the text added by inline autocomplete should not be removed.

[James Su, 2009-10-16 11:46:28]

I just updated this CL to fix issue http://crbug.com/23107 as well, as it's just
an one-line fix.

Regards
James Su

[Daniel Erat, 2009-10-16 18:59:56]

OK

http://codereview.chromium.org/287005/diff/5001/6001
File chrome/browser/autocomplete/autocomplete_edit_view_gtk.cc (right):

http://codereview.chromium.org/287005/diff/5001/6001#newcode806
Line 806: GtkTextIter sstart, send;
Mind renaming these to "sel_start" and "sel_end"?  These variable names are
really vague (and "send" is an completely unrelated word).

[James Su, 2009-10-16 23:41:41]

CL Updated.

http://codereview.chromium.org/287005/diff/5001/6001
File chrome/browser/autocomplete/autocomplete_edit_view_gtk.cc (right):

http://codereview.chromium.org/287005/diff/5001/6001#newcode806
Line 806: GtkTextIter sstart, send;
On 2009/10/16 18:59:56, Daniel Erat wrote:
> Mind renaming these to "sel_start" and "sel_end"?  These variable names are
> really vague (and "send" is an completely unrelated word).

Done. I have the same feeling when I saw it.