121752 - netscape.com - The button "Hide Left Frame" doesn't work.

Status: RESOLVED WONTFIX

(Tech Evangelism Graveyard :: English US, defect, P3)

Description

[Calvin Liu]

From Bugzilla Helper:

User-Agent: Mozilla/5.0 (X11;U;SunOS sun4u;en-US;rv:0.9.4) Gecko/20020122

BuildID:    Mozilla/5.0 (X11;U;SunOS sun4u;en-US;rv:0.9.4) Gecko/20020122

The button "Hide Left Frame" doesn't work.

Reproducible: Always
Steps to Reproduce:
1.visit the url
2.press "Hide Left Frame" button
3.wait to see the result

Actual Results:  nothing happens

Expected Results:  The left frame is hide and the "Hide Left Frame" button 
changes to "Show Contents".

It's correct in IE.

Comment 1

[Peter Trudelle]

->HTML Frames

Comment 2

[Kevin McCluskey (gone)]

Bulk re-assigning all of Eric's HTMLFrame bugs to John.

Comment 3

[Håkan Waara]

Worksforme with Mozilla RC1.

Bz, Calvin; can anyone else reproduce this in a recent build?

Comment 4

[Boris Zbarsky [:bzbarsky]]

Yeah, I'm seeing this with linux trunk build 2002-05-03-21....

Comment 5

[Pete Zha]

Still not work on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3)
Gecko/20020523

Comment 6

[Pete Zha]

Attachment: testcase(zip) using location.reload()

testcase using location.reload() instead of history.go(). This works fine with
mozilla

Comment 7

[Pete Zha]

Attachment: testcase(zip) using history.go(0)

testcase using history.go() in navbar.htm
mozilla doesn't work with this testcase.

Comment 8

[Pete Zha]

I found the problem is history.go(0) in a frame will cause the main frame(the
frame set) reload. So the "state" in main frame will always be 1 after the
button click.

Comment 9

[Pete Zha]

radha: How do you think this bug?
Call history.go(0) in a child frame will case the top frame reload.
If I change history.go(0) to location.reload(), it will work fine. Because it
only reload the child frame itself. So the parent.state will not be reset.
Netscape 4.x and IE works well, they will not reload the top frame when call
history.go(0) in a child frame. Need your input here. Thanks!

Comment 10

[Radha on family leave (not reading bugmail)]

In NS 6.x and above the Javascript history object is tied to the window's
session history object. So all JS history.back()/forward()/go() will function as
if you  pressed on the back, forward buttons and go menu on the toolbar. NS6.x
no longer supports the frame specific history operations that NS3-4.x supported.
This has been done for modularisation and easier management of history. Like you
have noticed, location.reload() in a frame will do a reload only in the frame. 
There is no plan to revert the current behavior of the JS history object. 

Comment 11

[John Keiser (jkeiser)]

Dunno whether Netscape really wants to bother changing the 3.0 JavaScript Guide,
but if it does, heeeeere's Evangelism!

Comment 12

[Bob Clary [:bc] (inactive)]

I say wontfix. 

Comment 13

[Bob Clary [:bc] (inactive)]

tech evang june 2003 reorg