Let me decide how deeply I can link into a site, not the designer.

cc: bz who's been doing some referrer stuff lately

confirming rfe. This _could_ be done.... Three (maybe two) things would need to happen: 1) Automatically store referrer (using document.referrer?) when page is bookmarked. 2) Provide UI to edit the referrer. (is this needed?) 3) Modify the openItem method in bookmarks.xml to use the referrer. This would require fixing openTopWin to take a referrer argument and do something useful with it, in particular....

I can see a need/desire for 2 under the following cirumstances: 1) Existing bookmarks, prior to feature introduction 2) Imported bookmarks from other apps bz: this is definatly an "if you ever have time to kill..." request. Just something I thought would be nice if it existed.

Doing this automatically would - in my interpretation - be a violation of the HTTP spec (RFC 2606). "The Referer field MUST NOT be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard." I vote for making it a field in the bookmarks properties *only* and let the user specify the Referer manually or to always just send the server root as Referer (compare recent comments in bug 55477).

Something to keep in mind if this is ever done: JavaScript bookmarklets often use the referrer, but some people find that this confuses server logs. See bug 122668. It would be nice if bookmarklets could choose whether to use the current URL (default behavior), a specified URL, or no page as the referrer. I like Mozilla's current behavior. I would like to see the referrer stored in bookmark properties even if it is not sent when using a standard bookmark. For JavaScript bookmarklets I'd like it to continue to send the current page as referrer since I believe it would break too many bookmarklets to do otherwise.

MASS-CHANGE: 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

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