Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1a3) Gecko/20060612 BonEcho/2.0a3 Steps to reproduce: 1. Download the two testcase files to the same directory. 2. Open testcase.html and click the install microsummary link. 2. Then go to Bookmarks > Add Bookmark and open the dropdown. Results: The microsummary is not displayed in the dropdown. Expected results: Microsummary is available for use. I'm also seeing the following error in the JS console: Error: [Exception... "Component returned failure code: 0x804b000a [nsIIOService.newURI]" nsresult: "0x804b000a (<unknown>)" location: "JS frame :: file:///home/aguthrie/downloads/2006-06-12-04-mozilla1.8/components/nsSidebar.js :: anonymous :: line 185" data: no] Source File: file:///home/aguthrie/downloads/2006-06-12-04-mozilla1.8/components/nsSidebar.js Line: 185 Myk had originally said he thought this had to do with file:/// URIs, but this happens when you upload stuff to a webserver, too.
To fix this, we probably have to make the addMicrosummaryGenerator method of the sidebar component interpret such URLs relative to the base URI of the page calling that method. It's unclear how complicated or significant a change that is, so targeting this to Firefox 3 for now, but if we get a fix in the beta2 timeframe, and it looks like something we could take in that release, I'll retarget.
The microsummary code in nsSidebar.js could probably just set the third arg of newURI() [to the page URI, instead of null], which looks like it should make relative URIs work. I'm curious if the other sidebar services work with relative URIs...
(In reply to comment #4) > The microsummary code in nsSidebar.js could probably just set the third arg of > newURI() [to the page URI, instead of null], which looks like it should make > relative URIs work. Except that nsSidebar.js has no way of knowing the "page URI". Bug 334875 provides such a way, it blocks some similar potential improvements to the search code (e.g. bug 340604).
Hmm, good point. I've added a note to http://developer.mozilla.org/en/docs/Creating_a_Microsummary
- BUGSPAM - Wontfixing all Microsummaries bugs, since the feature has been removed from the core product and previous versions won't get further fixes for it. If interested in supporting Microsummaries in your add-on, you're free to use our old microsummaries code and to search all previously open bugs by looking for [microsummaries-feature-removal] in the status whiteboard field.