Closed Bug 61047 Opened 24 years ago Closed 24 years ago

[Cache problem] pages not loading, after onkeypressed

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

Product:
Core
Component:
DOM: UI Events & Focus Handling
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 56063

People

(Reporter: jhvr, Assigned: bugs)

References

(
URL
)

Details

1 - Wait for the second window to open (start.html will load after index.html).
2 - press home in the menu on this page.
3 - click on this page.
4 - press F for fun or I for Info page.
5 - if this worked, press the other key.

P.s. On javascript console strange error line: 0 column: 0 in ...??? Take a look
at it!
Keywords: helpwanted, verifyme
focusedWindow.location has no properties is also on the javaconsole!
Line 105, first line 117, but it seems the source has been changed the last days.
Must be in navigator.js, yes I belief it was!

Please help me with this one! Hello, anyone out there???
Summary: After pressing a key, the page is not loaded into a frame → Page not loaded, after pressing a hotkey on this site
HJ, your page works just fine for me, keyboard navigation and all. Only the N 
for Next and the B for Back don't work, but I assume they're not implemented. I 
do get the same javascript errors as you, but I wouldn't worry too much about 
it, Mozilla is probably worried because you open tons of frames at the same 
time. Using build 2000113004 on win32.
Btw, congratulations, it's a well-designed page :-)
Fabian.
First: the N for Next and the B for Back are implemented also. I am using the
latest build to verify. But still no success. You need to type in several times,
to trap the error. It has to do with pageloading in a frame. Further, there are
only two, frames in the new window. I am unable to load a page, in a frame,
after an key event is trapped! Also, there where times that the page was loaded
in the wrong frame. The problem still exists, hope for a fix, or workaround.

Who's the one providing the fix or workaround? Please help!

And Fabian, Thanks for that nice comment.
I'm testing a workaround for this problem. Seems to work, hope someone else will
take a look at it to.

Just jump by at the URL above.

Man I hope it's fixed now, it drive's my crazy!
the focusedWindow error in console is caused by bug 56063. Marking dependancy.
Depends on: 56063
Taking the wrong keywords out, changed prio and summary
Keywords: helpwanted, verifyme
Priority: P3 → --
Summary: Page not loaded, after pressing a hotkey on this site → [Cache problem] pages not loading, after onkeypressed
Ben-any idea if this is actually a duplicate of bug 56063 instead of just a 
depencency?  thanks -d.
QA Contact: lorca → tever
By setting the cache, in the preferences menu, to 0 the problem is solved!!
I don't think this is joki's bug. Reassigning to ben for now, since he has bug
56063. Or is this Networking: Cache?
Assignee: joki → ben
Definate duplicate of bug 56063. The other error on the page has disppeared.
Marking as such.

*** This bug has been marked as a duplicate of 56063 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
No longer depends on: 56063
Resolution: --- → DUPLICATE
I don't think it's a duplicate... this is clearly a cache problem while bug 
56063 is about the commandDispatcher being null. No relation between those two 
except the javascript error on the console. I don't know what you think, but a 
bug in Event Handling with [Cache] in the summary dupped to a bug in 
XPToolkit/Widgets seems uncorrectly triage.
Fabian.
Keyser, two words for that one, work around.
verified
Status: RESOLVED → VERIFIED
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.