Bug 106715 - Navigation bar skips records when using the mouse to select “next record” or “previous record".
Summary: Navigation bar skips records when using the mouse to select “next record” or ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
5.0.0.5 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-23 06:23 UTC by Wayne Monson
Modified: 2017-12-04 12:39 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Monson 2017-03-23 06:23:02 UTC
Description:
When attempting to navigate through various records in LibreOffice Base 5x with the mouse, clicking the “next record' button or “previous record” button results in a selection that skips one or two records each time.

Steps to Reproduce:
1.Create a form with sixty or more fields.
2.Enter some data in sufficient fields to make five or six records and save.
3.Now try to navigate forward and backward to each record with the mouse.

Actual Results:  
Attempts to advance to the next record results in one or two records being skipped.  Similarly attempts to move to previous record results in one or two records being skipped.

Expected Results:
Navigation of records should work flawlessly with the mouse regardless of the size of the form.


Reproducible: Sometimes

User Profile Reset: No

Additional Info:
This bug has been observed in all versions of Base 5x I have tested to date including 5.3 and not in any versions of Base 4x that I have tested previously.
                                         
Note that  navigation of records works as expected when one uses the keyboard:  Ctrl + Alt + R arrow, or  Ctrl + Alt + L arrow keys regardless of the number of fields in the form in Base 5x.


User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
Comment 1 Xisco Faulí 2017-03-23 10:23:22 UTC Comment hidden (obsolete)
Comment 2 Wayne Monson 2017-03-23 16:55:39 UTC
Hi there,

The form I am working with is for my company and does contain sensitive information.  In fact, the company considers the very nature of the form to be confidential at this time.  So, I will need some time to develop a fictitious database in order to help you further.

In the meantime, some additional information about this bug report:  when I deleted fields from the form I was working with to less than sixty, I was able to use the mouse to navigate to the next and previous records as expected.

Given these parameters, I am hoping that I have provided sufficient information for the development team to investigate this bug further despite the status of my bug report at present.  While I can appreciate there are lots of bugs to attend to, I would be disappointed to see this matter put on hold.  While this bug is probably not considered critical, it is significant enough that my company will likely be looking for another solution than LibreOffice to meet its needs in the immediate future.
Comment 3 QA Administrators 2017-10-30 10:54:26 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2017-12-04 12:39:18 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20171204