the back button in the browser does not work on the web page www.theregister.co.uk. to reproduce the bug, got to the web site, view one of the articles and try going 'back'. nothing happens.

Works for me

sorry, but i cannot confirm this. i downloaded the latest build today and it still did not work. maybe this has something to do with entering the url manually in the address bar. e.g. enter 'www.altavista.com' and download it. then enter 'www.excite.com' and download it. when you press the back button, you don't get back to altavista.

chrisd, could you check with latest build of both Viewer and Apprunner please. If works fins, please mark Verified. Thanks!

Using 4/6 build on Win 98, Win 95, Win NT, Mac8.5 and Linux. Open the URL at www.theregister.co.uk in Viewer and Apprunner: Results across platforms: Apprunner: click on article, then click on 'Back' - nothing happens. Viewer: click on article, then click on 'Back' - does not go back to www.theregister.co.uk but goes back to previous page (Gecko home page or whatever other page was up) Reopening bug.

Troy -- I think this bug belongs to joki. If you agree, can you forward it to him? Otherwise, tell me who it should go to.

Nisheeth, another web shell issue

This works in the latest builds. Please re-test.

Tested again using 4/8 builds. Results are exactly the same as when I tested on the 4/6 builds (refer to comments). Bug behavior still exists. Reopening bug.

Adding URL to bug...

OK, so the behavior reported by e9026662@student.tuwien.ac.at is fixed, i.e., going to altavista followed by excite and then hitting back works. But, the behavior reported by chrisd, i.e., going to www.theregister.co.uk followed by an article and then hitting back does not work properly. This is a bug in history navigation on pages with framesets. Marking this for M5.

Clarifying 4/9 comments, the bug reported regarding the page http://www.theregister.co.uk was not reported by me. It was reported by the original reporter (see initial comments). I am the QA contact.

Setting component to Embedding APIs.

Moving history and link clicking related problems to M6...

Moving non-crashing layout and webshell component bugs to M8... I already have enough blockers and crashers for M6. If I fix them in time for M6, I'll move some of these bugs back to the M6 milestone. I'm keeping the M7 milestone for fixing XML bugs.

Updating summary to reflect that this is a history related problem.

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

Verified Dup of Bug 2005