Closed Bug 103436 Opened 23 years ago Closed 14 years ago

`Top' in Links Bar needs a better name

Categories

(SeaMonkey :: UI Design, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mpt, Assigned: jag+mozilla)

References

Details

Build: 2001100508, Mac OS 9.1

To reproduce:
1.  Go to <>.
2.  Look at the first link in the Links Bar.

What you see:
*   `Top'.

What you should see:
*   `'.

Details (this is cribbed from my ancient spec for the LINK UI):
*   If the author provides a title for the home/top/first/start link, that
    title should be used as the label for the link (cropped, if necessary, so
    that the title+icon+padding takes up 20 percent of the width of the bar).
*   Otherwise, `Site home' should be used.

This will make it much easier to understand the purpose of the link. It will
also make it clearer where the link leads, when a page is part of a sub-site of
a sub-site of a site etc.
D'oh. Corrections:

- 1.  Go to <>.
+ 1.  Go to <http://www.useit.com/alertbox/20010930.html>.

- What you should see:
- *   `'.
+ What you should see:
+ *   `Homepage for Jakob Niels...'
Blocks: 103053
I think "top" and "first" need to be consolidated.  I'll try to dig up my draft
spec and see what I thought we should do with them...
Assignee: blakeross → choess
OS: Mac System 8.5 → All
Priority: -- → P3
Hardware: Macintosh → All
Target Milestone: --- → mozilla0.9.6
Blocks: 103469
On further thought, I don't know if I like the idea of button title(s) in the 
toolbar changing with every page; I'm nervous about the effects it will have on 
consistency.  Isn't it enough that the "title" attribute is displayed on 
mouseover of the button?
If the name changes dynamically, the buttons will move around as I move from 
site to site.  I'd prefer if "up" would stay in a constant position, at least.
we need consistently across the web, not dynamic changing ones.. I vote if you
want dynamic changing buttons then add them so they show when a page uses them,
but dont drop the core button functionality, maybe they should hide those
buttons that aren't used on a page.  That is just plain wrong and silly.  That
is why this is a standard and it should stay that way, so when a user hits one
button, it will provide the same functionality accoss all web sites, just the
the back and forward buttons do for the navigator bar.  

As an anology, what would your car be like if you had 3 wheels that were
standard and 1 dynamic changing wheel.  The world would suck if we didn't
provide a minimal set of fixed things to rely upon.
what happens when if you are adding site dynamic ones the toolbar is not out
past the webbrowser size.. what will you do.  (I think toolbars by themselves
should have ([<] tool bar content in middle [>]) i.e. side scrollers.. Tabs will
suck because of the lack of side scrollers too.  Maybe I'll file that one under
[RFE].
posted bug 103543 for side-scrollers.
TITLE goes in the tooltip.  Names stay the same for UI consistency.

I agree that Top is a sucky name.  Site Home seems much better.  The W3C seemed
determined to avoid providing any link type that meant a link to a site's
homepage.  They yanked REL="Home" because Home is reserved to mean the user's
homepage or start page, but didn't provide a substitute...sigh.  I'd be happy
for coopting REL="Top" to unambiguously mean "Site Home".  That was sort of the
intent, anyway.
Here is page with a reference to top: http://www.htmlhelp.com/index.htm

it goes back to the main DNS entry.  Up should be to (_top - top of current
page).  The only thing I can say is maybe we need clarification here and rename
some of these items.. like 'Top' should be something like 'Site Home Page'.
I see the problem Matt seems to be having with screen size, is like most people
I see using an older mac monitor/crappy buildin video.. dont have the resolution
choices we have on the PC hense the need to clear up space here.. hmm.  Again..
another reason we need toolbar side-scrollers.
->claudius, who tests toolbars.
QA Contact: sairuh → claudius
How about "front" - as in the front page of the site, or the "store front"?
No longer blocks: 103469
Depends on: 103469
Waiting on spec completion, pushing to 0.9.7
Target Milestone: mozilla0.9.6 → mozilla0.9.7
according to http://fantasai.tripod.com/qref/Appendix/LinkTypes/ltdef.html#top

top == origin ==  the top of a hierarchy

I don't think this always refers to the front page of a site but it is kind of a
front/cover page

btw choess, mind retargetting this?
futuring
Target Milestone: mozilla0.9.7 → Future
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
Assignee: choess → jag
Priority: P3 → --
QA Contact: claudius
Target Milestone: Future → ---
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.