Closed Bug 65963 Opened 24 years ago Closed 23 years ago

focusedWindow.location JS error when reloading frames.

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 69712

People

(Reporter: shawn, Assigned: asa)

References

()

Details

If you go to the above site, the site loads with no JavaScript errors.  However, 
if you right-click in the left frame and go to "Reload Frame", two of the same 
JavaScript errors pop-up:

Error: focusedWindow.location has no properties.
Source File: chrome://navigator/content/navigator.js
Line: 137                   Column: 0

Then another one just like it.
On second thought, it looks like it happens if you right click in any of the 
frames and go to "Reload Frame".  Same thing each frame, each time.  Those same 
two JavaScript errors.
I get no errors. Tried all frames and they all reload without a problem.
Mozilla 2001011820 on Windows 2000 SP1.
I'm trying it on Mozilla 2001011904 and still having the problem.  You reload
the frame and it displays fine, yes.  But, two of the same JavaScript error pops
up in the console.

Error: focusedWindow.location has no properties
Source File: chrome://navigator/content/navigator.js
Line: 82			Column: 0

On Mozilla 0.7 it was line 137, now it's line 82 with this latest build.
Try creating a new profile and see if that fixes it.
I see the console errors. adding blake.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I also filed a bug about this issue weeks ago. My bug is marked as fixed, but
it's still not fixed. I see a lot of those navigator.js errors in frames.

But lately there's another error: window.offlineObserver line 530 and that one
is new to me!
I am having the same problem, even in Mozilla 0.8.1.
However, I am getting the error on JavaScript code which looks like this:

opener.location.reload();

(Called from a new window opened by the page)
See also bug 69712, which reports a similar error in the JS console and also
involves frames.
Either this bug should be a dup of bug 69712 or vice versa.

*** This bug has been marked as a duplicate of 69712 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.