Bug 104057 - REPORTBUILDER - Mouse over on scrolled down rules in conditional formatting dialog always brings back top rules in view
Summary: REPORTBUILDER - Mouse over on scrolled down rules in conditional formatting d...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Database-Reports-Builder
  Show dependency treegraph
Reported: 2016-11-20 10:54 UTC by Mario Bianchi
Modified: 2021-07-15 03:36 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Sample Database with issues, as requested (27.59 KB, application/vnd.sun.xml.base)
2016-11-20 21:29 UTC, Mario Bianchi

Note You need to log in before you can comment on or make changes to this bug.
Description Mario Bianchi 2016-11-20 10:54:09 UTC
Repro sequence:

1) Insert a text box item in a report detail section
2) Add many (I have 12) conditional formatting rules for the newly added item
3) Close conditional formatting dialog
4) Reopen conditional formatting dialog
5) Scroll down so that first rule is no longer visible
6) Hover with the mouse pointer on buttons like background color, foreground color etc. for one of the visible items

Here, when doing step 6, the top items in conditional formatting rule are shown in place of the currently visible ones; this is very annoying in that makes quite difficult editing items other than the first one.

Also, more often that not, when this happens LibreOffice Base crashes aftert closing the conditional formatting dialog.
Comment 1 Mario Bianchi 2016-11-20 11:20:43 UTC
Reported on LO release.

Also tried wiping the user configuration but nothing changed.
Comment 2 Robert Großkopf 2016-11-20 20:09:02 UTC
Please add an example-database. I won't create a report with so many formatting-rules for one field to see, what is happening afterwords.
Comment 3 Mario Bianchi 2016-11-20 21:29:38 UTC
Created attachment 128896 [details]
Sample Database with issues, as requested

Just look at the Team name text boxes, they have all 12 rules for conditional formatting. The problem happens every time on them as described.
Comment 4 Alex Thurgood 2016-11-21 10:18:48 UTC
I have no idea how to reproduce this, even with the sample db provided.

If I open any of the reports in Edit mode (select report with mouse, context menu Edit), and insert a blank text field, there are no options available to me in the Conditional Expression dialogue.

Checking the properties of the already existing text boxes in Detail section of  the report doesn't bring me any further - I don't seem to be able to find any Conditional Formatting examples.

For those of us who don't use Conditional Formatting everyday, please explain step by step how to reproduce this.
Comment 5 Mario Bianchi 2016-11-21 21:27:39 UTC
1. Open the "Classifica" report in edit mode
2. Click and select the first text box from left (the "=TeamName" one)
3. Choose the "Format -> Conditional Formatting" menu item from the top bar menu
4. Enjoy the 12 rule conditional formatting that exhibit the above mentioned bug and easily make Libreoffice crash...

Hope it helps,
Comment 6 Alex Thurgood 2016-11-22 10:57:17 UTC
Confirming with

Build ID: d54a8868f08a7b39642414cf2c8ef2f228f780cf
Threads CPU : 2; Version de l'OS :Mac OS X 10.12.1; UI Render : par défaut; 
Locale : fr-FR (fr_FR.UTF-8); Calc: group

I can reproduce both the misbehaving display jumping up to the first conditional format on mouseover of a lower conditional format attribute button, and the crash when the dialog is closed by clicking on the dialog window close button.
Comment 7 Alex Thurgood 2016-11-22 11:04:53 UTC
The crash is a separate bug (VCL related) from the UI bug. I will open a separate report for that.
Comment 8 Julien Nabet 2016-11-22 11:08:11 UTC
Alex: I'm stuck on Linux to give a try (see http://nabble.documentfoundation.org/Build-fail-on-Linux-ExternalProject-nss-mk-td4199999.html). On MacOs, I can give it a try but I'm less acustomed to use Mac (above all because of special Mac keyboard) and it's quite slow (compared to Linux).
Comment 9 Alex Thurgood 2016-11-22 11:21:51 UTC
(In reply to Julien Nabet from comment #8)
> Alex: I'm stuck on Linux to give a try (see
> http://nabble.documentfoundation.org/Build-fail-on-Linux-ExternalProject-nss-
> mk-td4199999.html). On MacOs, I can give it a try but I'm less acustomed to
> use Mac (above all because of special Mac keyboard) and it's quite slow
> (compared to Linux).

Julien : my guess is that the event trigger is incorrect here with the UI problem, for some reason a mouse over event on a lower placed conditional format entry within the dialog window (even if expanded to exclude vertical and horizontal scrollbars) causes a redraw or refresh of the contents of the window and resets to the first entry.
Comment 10 Alex Thurgood 2016-11-22 11:22:54 UTC
My lldb session doesn't display anything when the UI bug occurs, I guess that would require knowing where to set a breakpoint in the code...
Comment 11 QA Administrators 2019-07-15 02:48:24 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2021-07-15 03:36:31 UTC
Dear Mario Bianchi,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team