53026 - The back button doesn't work for pages retrieved by javascript

Status: VERIFIED DUPLICATE of bug 35340

(Core :: DOM: Navigation, defect, P3)

Description

[Ruairi Hickey]

CVS build from September 18th

After displaying my inbox in usa.net, I select a message to view...After reading
the message I cannot use the back button to get the previous page ie my inbox,
but hae to reload it again from the <inbox> link....

Comment 1

[Claudius Gayle]

i have a netscape.net account which uses the same usa.net setup and can confirm this

behavior with a 2000091905 Win98 build. The back button is lit up but unresponsive. History

dropdown and Go doesn't seem to work either. This may be frames related also?

Comment 2

[Greg Miller]

I've been experiencing similar problems with http://www.news.com/ as well as
pages disappearing from the history list. After reading the comments above, I
viewed the page source at news.com and found to my surprise that it's a frameset
leading to http://news.cnet.com/

I tried browsing news.cnet.com directly for a while, and I'm not experiencing
any of these history problems. It appears the frameset is the key to both the
lost pages and the lit-but-unusable back button.

Consequently, Bug 49404 may be the same problem.

Comment 3

[Radha on family leave (not reading bugmail)]

This seems to be related to document.write() a known bug assigned to pollmann.
marking dependencies

Comment 4

[Radha on family leave (not reading bugmail)]

This is because we don't have wysiwyg:// protocol handler in place. Giving it to
Eric who is dealing with wysiwyg. Not sure if he wants to mark this dupe of the
other one or mark dependencies.

Comment 5

[Viswanath Ramachandran]

nav triage team: Eric could you comment on the importance of this and how much 
time it would take to solve. thanks. 

Comment 6

[Eric Pollmann]

Marking dup of wyciwyg bug 35340

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

Comment 7

[Claudius Gayle]

VERIFIED Dupe