(1) Download and open file "Company_Cascading_Address_38 (mod).odb"
attached to bug 82844. Program displays window
"Company_Cascading_Address_38 (mod).odb" with <Forms> selected in
the left pane; the lower right shows the names of two forms.
(2) In the lower right pane, right-click
fCompanyAddres&Notes16-08-2014@12:16PM, and from the pop-up menu
select Edit. Program presents window
"Company_Cascading_Address_38 (mod).odb :
FCompanyAddress&Notes16-08-2014@12:16PM"; the icons in the forms
toolbar at the left are enabled.
(3) In the right side of the form click the table control "Address"
(not to be confused with the table controls "Bare Address" and
"Full Address"). Program draws a box with handles around the
(4) Right click on the control and from the pop-up menu select Form.
Program presents dialog "Form Properties".
(5) Click on tab Data. Observe that displayed Content type is "SQL
command" and the displayed content, at least the first line of it,
and a down-arrow at the right offers you the ability to expand the
(6) Click on the down-arrow to exapnd the box. The box expands to 5
lines; a vertical scroll bar at the right indicates that that the
box is showing about half the text.
(7) At the bottom of the scroll bar, click the down-arrow.
Program action expected: The top line of contents scrolls off the
top of the box and the next, previously unseen, line scrolls in at
Program action observed: The box collapses to the one line
I am setting bug priority LOW/minor because there are at least three
(*) Use the mouse wheel to scroll through the box.
(*) Use the keyboard to scroll through the box.
(*) The <...> button to the right of the field displays the Query
Design window for the SELECT statement.
Indeed, I think that WONTFIX would be a reasonable resolution.
This behaviour is present in bibisect-43all oldest and in my debug
build of master fetched 2014-08-13.
It's the same behavior in LO 3.3.0.beta1.
Scrollbars aren't working in any field of the form-editor and of the field-editor. You could see this behavior in the same form, when you open the listbox lbTypeOfCompany (label: Type Of Company) and have a look at Data → List Content.
... and not only by designing a form. The same when designing a report with the Report-Builder. Don't know why there isn't any existing bugreport for this.
Adding self to CC if not already on
First, a correction to the description of this bug: The report with
the referenced attachment is tdf#82884
The problem is still evident in daily dbgutil bibisect repository
version 2015-08-07 ...
Build ID: 09a9234c021ad98c5adeb493b5814e97b92ee912
Locale: en-CA (en_CA.UTF-8)
and in a daily build for Win32 ...
Build ID: 902255645328efde34ddf62227c8278e8dd61ff0
TinderBox: Win-x86@39, Branch:master, Time: 2015-07-30_03:52:07
Locale: en-CA (en_CA)
I am setting O/S All.
Migrating Whiteboard tags to Keywords: (preBibisect)
Only regressions should use the keyword 'preBibisect'. Removing it...
** Please read this message in its entirety before responding **
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 http://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!
Nothing changed in
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: kde4;
Locale: de-DE (de_DE.UTF-8); Calc: group
Scrollbar in properties a a form (or fields of a form) doesn't work when editing a form.
I still see the problem in bibisect-linux-64.6.3 repository on 2019-02-15.