NS_IMETHODIMP nsDocShell::ShouldAddToGlobalHistory(nsIURI* aURI, PRBool* aShouldAdd) centralizes all of the decision making for the process of deciding whether or not some URL type should be added to the global history. Should someone else come along and add a new type of URL, they have no means to decide for themselves whether or not they want their URL type to be added to the Global History unless they replace the nsDocShell with their own version.

At the same time we might want to say that action should be up to the embedder, not the URI provider.

This kind of hardcoding was a source of maintenance and even security woes in MozillaClassic. How about we get the list from some configuration file, or at least allow supplementing of a hardwired list from such a resource? Cc'ing the W-men for their resource/file expertise. /be

I understand the design issue here, but I don't know the (current) rules about which urls get added to history and which don't. Can someone state them?

-> jud

I'm thinking this piggybacks wherever the session history exposure stuff gets exposed (current thinking based on porkjockey's notes is nsIWebNavigation). nsIWebNavigation::Set|GetHistorySchemes(in|out wstring schemes);

travis is no longer @netscape.com changing qa contact to default for this component

over to alec.

coolness, I've been wondering about this.

Bumping off the mozilla0.9 train. If this needs to be in for mozilla0.9, please nominate nsbeta1. Right now, it's something on the radar that I'm not sure Alec is going to fix for 0.9. (At least, he hasn't told me so)

nav triage team; Sounds fairly straightforward to do, but not a high priority for nav team. Pushing out to mozilla1.2

*** This bug has been marked as a duplicate of 36867 ***

not a duplicate - I'm dumb.

mass moving lower risk 1.4alpha stuff to 1.4beta

5/5 EDT triage: minusing topembed+ status. Dropping this from the radar to better focus on existing working set.

adjusting summary - code moved to nsGlobalHistory::AddURI in Bug 224829

nsGlobalHistory::AddURI -> nsNavHistory::CanAddURI I think Firefox/XULRunner should accept "imap" and "news" on history, if someone (a 3rd party developer) implemented those protocol handlers. Probably it won't conflict with SeaMonkey and Thunderbird.