Bug 376189 started sending the frame's referrer as the referrer for the new load. I'm not sure this makes sense - shouldn't it send the current page, as we do in most other places where we trigger loads from the context menu?

(In reply to :Gavin Sharp (use gavin@gavinsharp.com for email) from comment #0) > Bug 376189 started sending the frame's referrer as the referrer for the new > load. If I remember correctly, the idea was to send the same referrer that was sent when loading the frame the first time, in order to avoid servers behaving differently if the page was displayed in a frame or outside of it. > I'm not sure this makes sense - shouldn't it send the current page, as > we do in most other places where we trigger loads from the context menu? When is this different? When there are several nested levels of frames maybe?

(In reply to Florian Quèze from comment #1) > If I remember correctly, the idea was to send the same referrer that was > sent when loading the frame the first time, in order to avoid servers > behaving differently if the page was displayed in a frame or outside of it. The referrer we send the first time is the frameset's location, as far as I can see.

So I think this is behaving correctly...

indeed, this is fine I guess