To reproduce: 1. Open a new browser window. 2. Click a link in that browser window to bring up a new page. (Try to pick URLs that will lead to content that overflows so you can actually try to page up/down). 3. Click in the content area so that it receives focus. 4. Page up/down. You'll see this on your console: "JavaScript Error: TypeError: controller has no properties" Note that it seems that _clicking a link_ inside the content area has something to do with clobbering the "controllers" (or whatever). Maybe we're not re-installing the controllers in the content area when we re-initialize the context? Also note that _clicking a link_ seems to be the thing that causes stuff to break: browsing to URLs from the personal toolbar, or typing a URL into the URL bar don't seem to cause the controllers to get clobbered.

I see this also when loading pages via bookmarks or by middle-mouse "pasting" into the content area. In fact, I haven't seen the page down key work at all in the browser window this year (on linux).

reproduced in 1/11 opt build. reassigning to saari as p3 for m14. BTW, there is no way this should be set to 'critical' severity. That is reserved for crashes, data loss or severe leaks. This should be set to normal.

ok, i concede that this isn't CRITICAL, but it is MAJOR. Hey, it's a web browser! you should be able to page up/down!

*** Bug 22407 has been marked as a duplicate of this bug. ***

*** Bug 22539 has been marked as a duplicate of this bug. ***

*** Bug 23656 has been marked as a duplicate of this bug. ***

BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.

See bug 24498 for some additional comments: this bug does not occur if you click in the URL bar first, and then the browser window.

Putting on pdt+ radar for beta1.

*** Bug 25365 has been marked as a duplicate of this bug. ***

qa-reassign to me. btw, would this bug also affect the use of the spacebar for scrolling? i'd think so, but lemme know if it's a different issue. thx!

Yes, the spacebar is almost certainly related. Basically, no key accelerators work consistently in the browser window.

*** Bug 25800 has been marked as a duplicate of this bug. ***

*** Bug 22830 has been marked as a duplicate of this bug. ***

*** Bug 25174 has been marked as a duplicate of this bug. ***

*** Bug 25703 has been marked as a duplicate of this bug. ***

*** Bug 25528 has been marked as a duplicate of this bug. ***

*** Bug 25938 has been marked as a duplicate of this bug. ***

Fixed thanks to a refresh machine running Linux, lots of help from Gramps, and a helping of Hyatt's brain.

Reopening -- with pointer focus, I still have lots of problems getting focus in the window to make page up/down and spacebar work, and I still frequently get into the mode that typing a space in a textarea scrolls the containing page down (bug 25938, which was marked as a dup of this one).

This is a problem with using point to focus, and moving focus in and out of the window, which is another known bug (19973). Hyatt and myself are working on focus memory right now which should fix this...

Fixed

joy! verif using linux: comm bits 2000-02-14-09 winNT: comm bits 2000-02-14-08 mac: comm bits 2000-02-14-13

*** Bug 36865 has been marked as a duplicate of this bug. ***