206531 - javascript: URLs need wyciwyg: caching and reload semantics

Status: RESOLVED WONTFIX

(Core :: DOM: Core & HTML, defect, P5)

Description

[Brendan Eich [:brendan]]

A document generated by a javascript: URL is just like one generated via
document.write.  The generating script shouldn't rerun on a reload, rather the
last generated page should be fetched from the cache via the wyciwyg: URL used
to capture the last generation.

The wyciwyg stuff seems tied into the content/html world.  How should
dom/src/jsurl code partake of it?

It would be good to fix this in 1.5.

/be

Comment 1

[Darin Fisher]

perhaps the wyciwyg protocol handler could be moved to a more generic location.
 then it wouldn't be very difficult to use here/elsewhere.  it is pretty generic
stuff.  there is only a little bit of code in nsHTMLDocument for talking to it.
maybe we should move it into docshell since it is related to session history? 
(xpfe/components/shistory should also be in docshell/)

Comment 2

[Christopher Hurley]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.8b2) Gecko/20050318

Confirmed this is still an issue in present build.

Comment 3

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.

Comment 4

[Andrew McCreight [:mccr8]]

FWIW, wyciwyg is being removed in bug 1489308.

Comment 5

[Andrew McCreight [:mccr8]]

Boris, should this be WONTFIX? It seems like if we aren't caching document.write, we wouldn't want to cache this either?

Comment 6

[Boris Zbarsky [:bzbarsky]]

Yeah, this is wontfix. Bug 836567 will make it so reloading a javascript: URL is just complete nonsense, but since that's what all other browsers and the spec do...