Closed Bug 10193 Opened 25 years ago Closed 5 years ago

Scroll by text block/Paragraph awareness

Categories

(Core :: DOM: UI Events & Focus Handling, enhancement, P3)

x86
All
enhancement

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: Crysgem, Unassigned)

References

Details

(Whiteboard: [19990901] Resolution: remind)

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.
Assignee: joki → janc
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.
Target Milestone: M15
Assignee: janc → joki
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
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → REMIND
With current bug counts I wouldn't expect this to happen by me in 5.0.  Setting
to remind.
Whiteboard: [19990901] Resolution: remind
Keywords: verifyme
Mass update:  changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer
Updating QA Contact.
QA Contact: ckritzer → lorca
Joki, is it time to remind you yet?:)

REOPENING, so you can Future it I guess.
Status: RESOLVED → REOPENED
Resolution: REMIND → ---
Yes, since Future seems to be the Remind of the current bug gods I'll change it 
to that.
Status: REOPENED → ASSIGNED
Target Milestone: M15 → Future
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
QA contact updated
QA Contact: gerardok → madhur
removing myself from the cc list
QA Contact: madhur → rakeshmishra
*** Bug 166018 has been marked as a duplicate of this bug. ***
Summary: [RFE] Scroll by text block/Paragraph awareness → Scroll by text block/Paragraph awareness
QA Contact: rakeshmishra → trix
http://bugzilla.mozilla.org/show_bug.cgi?id=179125#c3

joki is no longer here
Assignee: joki → saari
Status: ASSIGNED → NEW
QA Contact: trix → ian
Keywords: verifyme
Assignee: saari → nobody
QA Contact: ian → events
Component: Event Handling → User events and focus handling

In the 20 years since this bug was filed, the web has changed a lot:

  • page navigation is largely standardized across multiple, competing web browsers
  • the mouse scroll-wheel is a common if not standard feature
  • high-resolution, LCD/LED monitors replaced CRT monitors
  • smart phones, tablets and laptops are common browsing devices
  • Firefox implements Reader Mode to help with page readability
  • web pages are not simple text, but are visually rich in colors, images, and video
  • CSS and JavaScript dominate page layout, making pages much more interactive

An idea whose time has passed, I don't see Firefox implementing this.

Status: NEW → RESOLVED
Closed: 25 years ago5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.