None of them is redundant, because it are two different functions:
- the go-button loads the URL stated in the URL bar
- the refresh-button loads the URL behind the current page

But i do think it would make sense to place those two buttons more
close to each other. For example, the refresh-button could be placed
between the go-button and the menu-buttons.

On 27 jan, 07:46, Glen Murphy <[email protected]> wrote:
> The go button also becomes a stop button during page load.
>
> Many many Windows users like using their mouse to press the go button,
> just like people like using the 'search' button on google.com. There's
> an argument that if we removed it, people would learn to press 'enter'
> and be happier as a result (IM software went through this transition).
>
> However, reload is used so frequently and has such well-defined
> behavior that we didn't want to mix it with anything else (by say,
> making a 'stop/reload' button, or making it not work as-expected after
> the user entered a URL that they didn't submit).
>
> Many mobile browsers have a combined go/reload button.
>
>
>
> On Mon, Jan 26, 2009 at 12:38 PM, idanan <[email protected]> wrote:
>
> > So I just discovered we have a Go button ;)
>
> > Well, I knew it was there, just didn't know what it was used for, so
> > here goes:
>
> > We have both a Reload button (Circular Arrow) and a Go button
> > (Triangle). Hopefully this
> > won't trigger a war of Reload vs Go, but isn't one of them redundant?
> > They do the same
> > thing most of the time, both of them reload the page.
>
> > The difference in behavior is that if someone types a URL in the
> > location bar without
> > pressing Enter or clicking Go, then reload loads the currently
> > displayed page. Are
> > there any other differences?
--~--~---------~--~----~------------~-------~--~----~
Chromium Discussion mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-discuss
-~----------~----~----~----~------~----~------~--~---

Reply via email to