Bug 139069 - LISTBOX: Input of more than one entry impossible without switching to separate button
Summary: LISTBOX: Input of more than one entry impossible without switching to separat...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
: 145888 (view as bug list)
Depends on:
Blocks: Form-Controls
  Show dependency treegraph
 
Reported: 2020-12-19 15:56 UTC by Robert Großkopf
Modified: 2021-12-15 16:58 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Großkopf 2020-12-19 15:56:33 UTC
Open a Writer document.
Draw a listbox (Form → List Box).
Ignore the wizard, which will appear (with a permanent error here).
Go to Control Properties → General → List entries
Try to input more than one value pressing "Shift" + "Enter" at the end of the first value.
Nothing happens.

This has been the normal behavior to enter more than one list entry since the beginning of LO. Works in LO 6.4.6.2, fails in LO 7.0.4.2 under OpenSUSE 15.1 64bit rpm Linux.

Now you have to change the entry by pressing the button at the right of the input box. Could be it is a new "feature", but for a normal user this behavior is a regression.
Comment 1 Xisco Faulí 2020-12-21 14:19:19 UTC
This is the expected behaviour since the separate button was added
Comment 2 Robert Großkopf 2020-12-21 15:04:58 UTC
(In reply to Xisco Faulí from comment #1)
> This is the expected behaviour since the separate button was added

This couldn't be the reason to set it to WONTFIX. The separate possibility by a button is here also in LO 6.1.5.2. You have only to press on the right like in listboxes.
I will set this back to unconfirmed, because it is a regression: One possibility to input values is lost. No other possibility has been added by the button.

When I try to edit forms since LO 7.0 I think target is: Let us design is for nice looking, nobody will use it.
Comment 3 Xisco Faulí 2021-02-23 08:50:15 UTC
Reproduced in

Version: 7.2.0.0.alpha0+ / LibreOffice Community
Build ID: 26d23c96d449c201e50df04023d9cbfd59d3d133
CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 4 Aron Budea 2021-03-11 02:19:32 UTC
(In reply to Robert Großkopf from comment #2)
> I will set this back to unconfirmed, because it is a regression: One
> possibility to input values is lost. No other possibility has been added by
> the button.
The change was introduced by the following commit, bibisected using repo bibisect-linux-64-7.0.

https://cgit.freedesktop.org/libreoffice/core/commit/?id=1efeb17837c22499f00299c033ae59ba3910f7d7
author		Caolán McNamara <caolanm@redhat.com>	2019-11-04 13:06:04 +0000
committer	Caolán McNamara <caolanm@redhat.com>	2019-12-09 13:28:35 +0100

"weld Property Browser"

...
"Also replaced the other strange Edit-alike TextView with a real Edit entry and
a dropdown which can be used to support entry of multi-line labels"

Seems like the change was intended. Not sure what is possible here, perhaps if clicking on the edit field would bring up the text editor dropdown, that'd be nice (as I can see, even in the previous version, the edit field itself was non-functional, edits happened in the editor dropdown).

What's different in the dropdown is that pressing Enter no longer closes it. No idea what other way would be to switch between the editor and the button, Tab doesn't work (it adds a Tab to the editor, it probably shouldn't).

It's also annoying that when trying to select text in the dropdown, if you move outside the dropdown area, it closes (users will likely select from right to left, because it's easier to start from the large empty area, but if they're just a bit off with the movement, the popup closes).
Comment 5 Dieter 2021-12-15 16:58:28 UTC
*** Bug 145888 has been marked as a duplicate of this bug. ***