[Libreoffice-bugs] [Bug 81829] VIEWING: Can't page down accurately in "Entire Page" view

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=81829

--- Comment #22 from P Cunningham <patrick at scphotographic.com> ---
Forgive me, Mr Foote, but you seem to have closed your mind to the possibility
of this being a bug and are therefore refusing to engage properly with the
problem.

The solutions you have offered are mere workarounds. A workaround is a
temporary measure for achieving a necessary or desired function which is not
available in the software, which can be used, though not fully satisfactory,
until the useability issue is addressed in the programming. It is not a
solution to the problem in itself.

And in this case, the workaround you suggest does not even address my issue.

The resolution I am working at does not display a whole page of text; I can see
about half a page on the screen. Therefore, moving to the top of the next
document page does nothing to help - I need to go to the next section of the
page, which begins on the next line below the one currently displayed on the
screen.

In other word processing programmes I can do this easily. I press pg-dn and my
view of the page moves so that the line which is currently the last line on the
screen becomes the first or second line, enabling me to read on, uninterrupted
by the need find my place.

You have again repeated a clearly inaccurate statement; you say "the PgDn/PgUp
scroll controls which vary widely depending on os/DE,"

I explained that I can reproduce the issue on both Windows 10 and Mac Mojave;
another post on this thread states that the issue on which this thread is based
- which is different but obviously has its roots in the same bug - can be
reproduced in Linux too! Your thesis that this is an OS issue is therefore
unfounded.

You state "correcting by LO is of questionable utility". I disagree. For me and
for many others this is a fundamental useability issue which should be
addressed.

While I am pretty computer literate (my first job in computing was in 1967,
programming an IBM 1130 in Fortran using punched cards - look it up!) I have
not followed a career in IT. I am therefore not familiar with modern coding,
but identifying why this renegade behaviour occurs should be fairly
straightforward, requiring just a few step-by-step executions of the relevant
piece of code. I would be grateful if you would either acknowledge that this
needs to be addressed, or direct me to some contact point where I can take it
further.

Please understand that I do appreciate what you do!

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20210326/3033c06f/attachment.htm>