Summary: | VIEWING/UI: Page-by-page navigation needs love | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Adrian Custer <acuster> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | hb, jbfaure, jmadero.dev |
Priority: | medium | ||
Version: | 3.5.4 release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
Adrian Custer
2012-06-19 14:06:42 UTC
(In reply to comment #0) > The current experience, ... only works consistently at just the right > level of zoom and ... True. > only works with the Navigation toolbar set to 'Page' and then clicking > on the 'next' and 'previous' (which I use at the bottom of the vertical > scrollbar). Page wide steps sometimes fail when more than one page is displayed on the screen. This is another bug. > There are three modes of input (of which I know) for page by page navigation: > * key presses on the 'PgUp' or 'PgDn' keys, False, this mode should be for screen by screen navigation as usual. > * mouse clicks on the Navigation toolbar/widget at base of vertical > scrollbar, True when the Navigation toolbar is set to "pages". > * mouse wheel incremental rolls, some integer number of which will > result in a full page move. Bug 42794 wants to change this. > I would expect similar or identical behaviour with all three. No, page by page is different to screen by screen. > Regardless of the state, the expectation is that the UI will skip ahead so > that an integer number of inputs (key presses, mouse clicks, scroll wheel > scrolls) will result in the UI being in the identical state to the initial > view but one page further in the document. Yes, but this is another problem. This report mixes at least two issues in one bug. Also the operating system used effects the scrolling. I recommend to split it up to the individual problems, search bugzilla and post then new reports. We don't update the version, ever, for these kinds of things. Leave a comment saying it's still an issue but please do not update version as it is used to see when the first request (or bug report) was made. Thank you The status of this bug report is still UNCONFIRMED because it does not describe a clear scenario to reproduce the offending behavior(s). As it stands its description is unusable. I will close this bug report as INVALID. If you are still convinced that, in the current active branches, there is something that goes wrong in this area, please file another bug report for each individual behavior with a scenario describing step by step how to reproduce it. Another way, is to discuss this question on the UX-advise mailing-list. Best regards. JBF |