W3C home > Mailing lists > Public > www-amaya@w3.org > January to March 2008

Re: scrolling, and losing keyboard input

From: Arlo Leach <arlo@arlomedia.com>
Date: Mon, 17 Mar 2008 10:39:30 -0500
To: <Irene.Vatton@inrialpes.fr>
CC: <www-amaya@w3.org>
Message-ID: <C403FAE2.6880%arlo@arlomedia.com>


> Hum, normally clicking on a position in the scrollbar skip to the position in
> the document . As Amaya doesn't have the whole document formatted (often too
> big), it re-formats the requested part. But often the position is not exactly
> the same and it seems inconsistent.
> We could limit the move to one screen up or down if you think it's the habit
> on MacOS

The option to jump to the point where I clicked, or jump one screen at a
time, is set in the system preferences, and mine is set to jump one screen
at a time, which I believe is the traditional Mac behavior. I can see that
Amaya is trying to jump one screen at a time, but sometimes it doesn't move
at all, sometimes it jumps more than a screen, and sometimes the document
goes blank until I click in the document.

It does look like this mainly happens with very long documents. I'm testing
a couple small documents now and the scrolling seems fine, but when I open a
long document and cut and paste sections around, the scrolling degrades.

I've tried using the page up and page down keys as an alternative to
clicking in the scroll bar. In this case the scrolling works well for the
first few pages, then eventually the document display will break up, and
I'll have to click in the document to redraw the display and see where I am.
I uploaded a screen shot of this issue here:


I blacked out my client name, but you'll see that a part of the document is
repeated and a part is cut off in the display.

> Perhaps that occurs after a specific operation. If you have a scenario that
> shows the bug, we'll be happy to fix the problem.
> For the moment we're not able to reproduce it. We continue to investigate.

I've been observing carefully, but I can't pinpoint this to any action that
triggers it. I think it has something to do with setting attributes and
possibly with entering an attribute value and pressing Return instead of
clicking the green checkmark icon, but that doesn't happen every time. It
might also be related to my long document. I'll see if I notice it on
shorter documents.

> Esc is sometimes kept by the window manager.

What I meant was that I can use Esc and F2 interchangeably until the
keyboard input stops, then I can use F2 but not Esc. The point is that some
keys continue to work, but most keys like all the alphanumeric keys do not.

Thanks for looking into this, and I'll post again if I can pinpoint the



Arlo Leach

Make friends with your computer
Received on Monday, 17 March 2008 15:40:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:39 UTC