Closed Bug 90966 Opened 23 years ago Closed 21 years ago

Apple using <link rel="find"> not meshing well with Link Toolbar

Categories

(SeaMonkey :: UI Design, enhancement, P4)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED
Future

People

(Reporter: lordpixel, Assigned: choess)

References

()

Details

www.apple.com actually uses <link> elements to aid site organization. With the
Link Toolbar finally getting close to landing, these can finally be used. Yay!

One of the <links> they provide is rel="find". Casual testing reveals this value
doesn't interface with the Link Toolbar's Search menu item.

Should we include "find" as a value we support for this?
Depends on: LinkUI
Status: UNCONFIRMED → NEW
Ever confirmed: true
IMO rel="find" should be synonymous with rel="search".  FWIW iCab treats it that way.  I don't see the search value in the current UI either.  Surprised myself that I didn't notice til now, since I feel that it is arguably one of the most important values as far as utility to the end user.
I've added the following to LinkToolbarHandler.js:

  function getLinkType(relAttribute) {
    switch (relAttribute.toLowerCase()) {
      ...
      case "search":
      case "find":
        return "search";
      ...
    }
  }

Which should turn up in a patch eventually.
I may have acted too soon.  Here's the link from apple.com:

<link REL="find" HREF="http://www.apple.com/find/">

However, http://www.apple.com/find/ is redirected to the SiteMap.  This may just
be an oversite on their part.  If you go the apple.com Extended Search page:

<http://www.apple.com/find/extsrch.html>

You'll see a link to the Simple Search page.  This URL is the same as the
rel="find" URL.  So it appears that rel="find" was originally intended to take
you to a search page.
Yeah, I noticed that. I think its just a bug on their part. Maybe I'll go file a 
bug with Apple ;) So this is fixed in the source now?

Do we leave this open till its checked in? I'm not sure...
Yes, this bug should stay open until working code is checked into CVS [1], which
is contigent on the Link Toolbar patch being accepted, hence the appropriate bug
dependencies.

It /was/ fixed in my source, but I'm waffling on that somewhat because of the
rel="find" linking to sitemap thing.  It would be nice if we could get some
clarification from Apple on this before "blessing" a new link type...especially
if apple.com is the only place it's used.
[1] or resolved another way, like WONTFIX
I just looked at this again, and I think /find/ (ie, really just /find/
index.html) *is* the simple search page. Its really bad UI (because you have to 
scroll to the bottom of the page to find the search input box) but its probably 
not "wrong" per se.

I mostly opened this bug wondering if "find" existed in any existing link element 
stanard. Seems like a sensible thing to support anyway though.
Blocks: 103053
The current incarnation does not link "find" to the Search menu item. However,
Apple seems to be using rel="find" to point to a site map, so I'm not sure we
should be doing this.

Google says Apple seem to be the only people using rel="find", so I suggest we
WONTFIX this.

Gerv
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Shouldn't this be evang and we evangelize apple?
Zach: at one point we were recognizing search/find in the toolbar, which we
don't do anymore.  After I get a spec written up of exactly what link types we
should support and how, we can fix this up again and evangelize Apple. 
Reassigning to myself for now and futuring.
Status: RESOLVED → REOPENED
Priority: -- → P4
Resolution: WONTFIX → ---
Target Milestone: --- → Future
Taking from mpt.
Assignee: mpt → choess
Status: REOPENED → NEW
Blocks: 103469
No longer blocks: 103469
Depends on: 103469
Component: User Interface Design → XP Apps: GUI Features
apple has changed its <link> to rel="index".

-> FIXED
Status: NEW → RESOLVED
Closed: 23 years ago21 years ago
Resolution: --- → FIXED
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.