[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV lynx2.7.1ac-0.20 available

From: Al Gilman
Subject: Re: LYNX-DEV lynx2.7.1ac-0.20 available
Date: Mon, 5 May 1997 08:59:15 -0400 (EDT)

  From: Hynek Med <address@hidden>
  Subject: Re: LYNX-DEV lynx2.7.1ac-0.20 available

  On Sun, 4 May 1997, Klaus Weide wrote:
  > Note that there have been some changes in the devel code regarding
  > WHEREIS behavior, already since lynx2.7.1ac-0.12 or so, on which no-one
  > has commented (maybe nobody has noticed).  They do not affect what is
  > searched (form fields etc.) but only how the screen is positioned
  > after a search, and whether the screen is refreshed (in some cases).
  I have noticed that what you searched for is highlited, and positioned in
  the middle of the screen - and I like it!
Laura Eaves uses a screen magnifier and starts with the
upper-left portion of the eighty by twenty four characters.  She
definitely prefers that the match which has been found be on the
top line of the displayed page.

She pointed out that speech users, at least many of them, have no
indication of text highlighting in their speech output.  This
still leaves me unclear as to what speech users would prefer.  If
one does a "read line" after the page loads, one might want the
hit to be on that line.  If one lets the page load and then does
a "read screen" it might actually be preferred to have a line or
more of context read off before the line with the hit in it is
spoken.  This is the notion that I was focused on when I first
suggested the change.

Of course, the eyeball behavior that I was not thinking about is
the ability to rapidly acquire the first highlight on the page,
and by shape recognition move to the top of the paragraph or list
that the hit is in.

It sounds as though a lynx.cfg configuration setting is the most
desirable out.  I think we can be reasonably confident that
people using one-line Braille displays, will also prefer that the
hit appear on the top line.

Feedback from speech users would be nice to have, but if
configurability is not a big deal, it may be possible to figure
out how to proceed without that feedback.

Al Gilman
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]