Re: Upcoming UI changes

[藍挺瑋 <lantw44 gmail com>]

於 週二，2016-10-11 於 08:57 -0500，Michael Catanzaro 提到：
> Hi,
>
> On Tue, 2016-10-11 at 18:43 +0800, 藍挺瑋 wrote:
> > I think it is bad to show only the domain.
>
> OK, enough people have complained about this aspect of the mockup
> that
> I have no plans to implement it.
>
> > Is it possible to keep the web page title shown in the header bar?
> > Most
> > desktop browsers show the title at the top of the window or using
> > it
> > as
> > the window title. It will be nice if Epiphany can keep this feature
> > because the URL is not always readable or useful.
>
> I don't think so, there's not really any room for page title anymore.
> Where would it go? Are page titles really important? I don't miss it
> at
> all.

I still like the old title box that packs the title and the URL in the
header bar because the URL usually provides less information to users
than the web page title. The old title box design is consistent with
other applications such as Evince and Gedit.

I am not sure why it had to flicker between the title box and the
entry. If the reason was that we could not know the title immediately
after it starts loading, can we show only the URL when the title is not
available like what Evince does when opening a PDF file without title,
and switch back to title and URL once the title is loaded?

> > Moving important functions such as viewing page source to the
> > context
> > menu doesn't look good to me.
>
> Funny story: when I started using Epiphany, I thought this feature
> did
> not exist, because other browsers have it in their context menus and
> I
> did not think to check the window menu!
>
> But yeah, we can definitely rethink how options are scattered between
> the context menu and the hamburger menu.

So it seems it is better to keep some functions in both menus as long
as it doesn't make menus become too long.

> > Some web pages disable the context menu
> > or replacing the context menu with their own menus. If we don't
> > keep> these functions in the hamburger menu, they becomes
> > inaccessible to> users unless there are keyboard shortcuts bound to
> > them, users
> > >  remember> shortcuts, and web pages don't disable shortcuts.
>
> On the rare sites that do override the context menu, you can always
> get
> the Epiphany context menu with a second right-click (sans bugs) so
> nothing should ever become inaccessible.

Thanks for the tip. I didn't know double right-click can do this.
However, it didn't always work for me. I tested it with Google Document
(https://docs.google.com/document/d/<string>) and Google Drive (https:/
/drive.google.com). It worked with the former but not with the latter.
Even if double right-click works without problem, I think it is hardly
discoverable by most users.

> > I even think we can
> > move 'Inspect Element' to the hamburger menu, so using the
> > inspector
> > on
> > web pages with context menu disabled can be easier.
>
> Inspect Element can't move because it depends on the element
> selected,
> right? We could add a generic 'open inspector' menu item though.

I forgot that it is possible to move focus to selected things in the
inspector with right-click on the page. Yes, I mean 'Open Inspector'
here.