Closed Bug 420878 Opened 16 years ago Closed 6 years ago

Add simplified web app breadcrumb support to refractor

Categories

(Mozilla Labs :: Prism, defect)

Product:
Mozilla Labs
Component:
Prism
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: mfinkle, Unassigned)

Details

Currently, refractor can sniff a web page for <link rel="webapp" href="uri-to-webapp-bundle"/> and prompt the user to install the webapp as a Prism app.

We should add simplified support like that found here:
http://codinginparadise.org/weblog/2008/02/pubtools-offline-enable-content-in.html

If you want a desktop shortcut icon, add shortcut="true" to the <html> tag:

<html shortcut="true">

Icon support:
<link rel="shortcut.icon" title="16x16" href="icon16x16.png"/>
<link rel="shortcut.icon" title="32x32" href="icon32x32.png"/>
<link rel="shortcut.icon" title="48x48" href="icon48x48.png"/>
<link rel="shortcut.icon" title="128x128" href="icon128x128.png"/>

and:
<meta name="shortcut.name" content="Test Application"/>
<meta name="shortcut.url" content="http://www.test.com/index.html"/>

Most of these have sensible defaults and can be left out:
'shortcut.name' defaults to the HTML TITLE element if not present.
'shortcut.url' defaults to the page's URL if not present.

Thoughts?
Sounds like a great idea to me.
The <link> tags for icon support seem decent.

I like the word "shortcut", which doesn't imply "desktop" and could be used equally well to populate an in-browser shortcut (i.e. bookmark) or an on-phone shortcut (f.e. home screen icon), although I wonder if it's really necessary to differentiate between a "shortcut" icon and an icon destined for some other use (especially for |rel="shortcut.icon" title="16x16"|, which seems identical to |rel="icon"|).

Also, use of the "title" attribute in this way is a bit of a hack, but it's not unreasonable.  An alternative would be to include the resolution in the relationship name ("32x32icon", "128x128icon", etc.), which might simplify retrieval and is a bit less hacky but might be harder for authors to remember.

Regarding the <meta> tags, shortcut.url doesn't make a lot of sense as a <meta> tag, since specifying URLs is what <link> tags are for.  And there are already link types that would work well here, including Start and Bookmark <http://www.w3.org/TR/html4/types.html#type-links>.

<link> tags also include a "title" attribute, so shortcut.name and shortcut.url could both be satisfied with a single <link> tag.  I think that's the better approach.
OS: Mac OS X → All
Hardware: PC → All
Just to note, the naming scheme used by PubTools maps directly to what Gears uses for the createShortcut function: http://code.google.com/apis/gears/upcoming/api_desktop.html

I agree with Myk on using a <link> tag to set up any URL and name instead of using <meta> kludges.

As for using shortcut="true" as it's specified by PubTools, I have to admit I don't see much point in having Refractor care at all what the website specifies, and instead leaving the decision whether to create a shortcut or not up to the user. (Currently, install-shortcut.js won't accept no for an answer when it comes to creating one or not.)

For the icons, the title attribute definition by the W3C is: "This attribute offers advisory information about the element for which it is set." Which means title="32x32" would be quite alright, since it's advisory information about the icon's dimensions.
Prism isn't maintained anymore. Mass closing of the bugs.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.