521568 - JavaScript history object reloads all frames when history.go(0) is used in one of the frames

Status: UNCONFIRMED

(Core :: DOM: Navigation, defect)

Description

[Jiri Hovorka]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; cs; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

Hello.

  I have filled this bug to 'Bookmarks & History' because there is no 'JavaScript' category.

  This report concerns JavaScript history object when using page with frames displayed by Firefox 3.5.3.
  Every time JS called history.go(0) function to reload page which resides in a frame, it reloaded ALL the frames (like clicking on refresh button). See attached example.
  There is not trivial, but simple workaround - change document.location (also included in attached files).

  I'm not sure if it is a real bug or just a feature:). I took a look on several JS references and there were no mentions of how history.* functions should behave when used in document in frames. Tt is unclear for me how this SHOULD work.
 The fact is that IE (8) and Opera (9.6, 10) reload ONLY the frame in which history.go(0) was invoked. I find their behaviour more logical than reload ALL the frames, but that's just my personal taste.

  What is the correct behaviour (if there is such a thing)?

Thank you,
J.Hovorka

Reproducible: Always

Steps to Reproduce:
1. build FRAMESET page
2. use history.go(0) in one of the frames in JavaScript

(see attached files)
Actual Results:  
reloads ALL the frames

Expected Results:  
Probably reload just the frame in which history.go(0) was called - i'm not sure, specifications are not clear:)

Comment 1

[Jiri Hovorka]

Attachment: Main file (index)

Comment 2

[Jiri Hovorka]

Attachment: top frame

Comment 3

[Jiri Hovorka]

Attachment: Bottom frame (with workaround)