69206 - forward button isn't disabled when should be (in frames)

Status: VERIFIED WORKSFORME

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

Description

[Casey Perkins]

In a frameset, click a link that changes one of the frames to a different page.
Now click back to return that frame to its previous page. Now click another link
that changes the page in one of the pages. The forward button should now be
disabled, but its not. It doesn't take you anywhere, but it is still "lit up",
not grayed out.
I have confirmed this bug on NT, 98 and Linux, so am marking OS as All.

Comment 1

[Keyser Sose]

Reporter what build are you using? I am unable to see this in the latest
nightlies because the Back Forward Buttons are greyed out all the time in Frames.

Comment 2

[Casey Perkins]

I am keeping up to date on my builds...Besides, Back/Forward are not always
greyed out in frames, but only when a) A frames page is your startup page or b)
You prevent your startup page from loading and then load a frames page.
Try going to a non-frames page, then go to a frames page to test this bug.

Comment 3

[timeless]

a) A frames page is your startup page
dupe of bug 56062 back/forward buttons don't work at first if first page is 
framed 
by way of bug 69207 

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

Comment 4

[Casey Perkins]

When you marked this bug as a duplicate, you were not paying close attention to
my last post. I was merely responding to Keyser Sosez's comment in which he said
he couldn't test my steps to reproduce this bug because back and forward buttons
were greyed out all the time in frames. My response was that they were NOT
greyed out at all times, but only under those circumstances that I mentioned,
(which, indeed, is bug 56062), and to try my steps by first avoiding getting
stopped cold by bug 56062.
The bug I'm describing does not have to do with the back/forward navigation
buttons being improperly DISABLED, but rather improperly ENABLED.
To once again describe what behavior I'm reporting in this bug:
In a frameset, click a link that changes one of the frames to a different page.
Now click back to return that frame to its previous page. Now click another link
that changes the page in one of the pages. The forward button should now be
disabled, but its not. It doesn't take you anywhere, but it is still "lit up",
not grayed out.

Comment 5

[timeless]

sorry

Comment 6

[Radha on family leave (not reading bugmail)]

I think the problem is with some notification to the back/forward buttons. After
step 3 when the forward button is enabled, click on it, it immediately becomes
disabled and takes you nowhere. The Go menu properly lists the 3 sites you visited. 

Comment 7

[Radha on family leave (not reading bugmail)]

The problem is with the update notifications sent to the back and forward 
buttons. Session History's list is fine. If you look at the Go menu, the check 
mark is at the right entry. The problem is either with browser's 
nsIWebProgressListener object OR in docloader which sends the notifications to 
the browser. First trying the browser team

Comment 8

[Viswanath Ramachandran]

reassigning to alec. 

Comment 9

[Paul Chen]

nav triage team:

Marking worksforme using 2001072604 mac mozilla build

Comment 10

[bcortez]

Paul,

Marking this as WORKSFORME when it only works on the mac platform seems 
incorrect to me.  The author mentioned that it was failing on Windows (NT, 98) 
and Linux platforms, he didn't mention macs at all.

I suggest this bug be reopend an tested on the operating systems mentioned by 
the author before being marked as WORKSFORME.

Just my, $0.02

Comment 11

[Tom Mraz]

Verified Linux 2001082021. Please verify on Win.

Comment 12

[sairuh (rarely reading bugmail)]

mass-verifying WorksForMe bugs which haven't changed since 2001.12.31.

set your search string in mail to "EmperorLondoMollari" to filter out these
messages.