Summary of request: Scrolling keys should recognize and align the viewport with text blocks, and perhaps certain discrete elements and markup Specifically, pressing a key (I say, ambiguously) would advance one to the next paragraph (both denoted by <P></P> and not), or header, or <HR>, whichever is next in document order - and align the top of it *precisely* with the viewport. Rationale: When reading a long document, most especially lengthy text-only essays, the utility of the scrolling mechanism (Page<Up/Down> keys, the <shivers> scrollbar's "thumb") is often - "imprecise" - enough to be diverting. When reading a long essay before a CRT, an activity itself difficult for some users, there is a tendency to recline and leave a single hand available for interface (for myself, usually at the keyboard, specifically the PageUp/PageDn set of keys). I am not presently reclining, and let those who doubt know that I am sitting upon a stack of empirical data printouts from users. In using the PageScroll keys, occasionally some co-adjustment with the mouse is required to align the verses with the viewport. Ergo forcing the user to employ once more two hands (no evolution jokes, please). This would also alleviate the microcephalic horror of the scrollbar thumb, which can be become microscopic and grossly overresponsive aside a long document.

This bug is assigned to joki@netscape.com? Ach, oh my. Better, the QA engineer assess the validity. Note, I do not advocate the installment of this behavior as the default. Implementation details are enjoyable to discuss further, but I do not judge this the venue.

Let me step in here for just a minute. We do not assign QA Contacts as the "Assigned To" development engineer. The QA contact always gets notified anytime a bug is touched, just by being the QA contact. If additional information is necessary, then just request the information in the bug and the QA engineer will do the investigation. By removing the development engineer from the bug and the discussions taking place within the bug will only inhibit them from staying on top of the issue. Please refrain from re-assigning the bugs to QA engineers in the future. Thanks

With current bug counts I wouldn't expect this to happen by me in 5.0. Setting to remind.

Mass update: changing qacontact to ckritzer@netscape.com

Updating QA Contact.

Joki, is it time to remind you yet?:) REOPENING, so you can Future it I guess.

Yes, since Future seems to be the Remind of the current bug gods I'll change it to that.

Reassigning QA Contact for all open and unverified bugs previously under Lorca's care to Gerardo as per phone conversation this morning.

QA contact updated

removing myself from the cc list

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

http://bugzilla.mozilla.org/show_bug.cgi?id=179125#c3 joki is no longer here