Bug 79176 - Input field editing changed from double-click to single-click
Summary: Input field editing changed from double-click to single-click
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2014-05-24 14:13 UTC by João Mac-Cormick
Modified: 2014-11-05 03:30 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Sample of form (48.98 KB, application/vnd.oasis.opendocument.text-template)
2014-08-19 09:33 UTC, Friedmann Bruno
Details

Note You need to log in before you can comment on or make changes to this bug.
Description João Mac-Cormick 2014-05-24 14:13:15 UTC
Window to edit the input field is not displayed.

Steps to reproduce:

1) Launch LibreOffice Writer
2) Select Menu "Insert-> Cross-reference…"
3) In the window "Fields", select "Functions" tab
4) Select "Type" "Input Field"
5) Type "test" in "Reference", and Press "Insert" button
6) In the window "Input Field", type the value 5, and Press "OK" button
7) In the window "Fields", press "Close" button
8) Double click in the "field" 5

Current behavior: When you double click in the input field, a window "Edit fields" is displayed.

Expected behavior: Show a window "Input Field", for editing the value.

Workaround: Press ctrl+shft+F9

Rwindows XP SP3
LibreOffice 4.2 branch, 4.3.0.0.beta1 and 4.4.0.0.alpha0+ (TinderBox: Win-x86@42, Branch:master, Time: 2014-05-22_01:05:33)

Note: The branch 4.1 and earlier have correct behavior.
Comment 1 Firas Hanife 2014-05-24 17:30:57 UTC
I can reproduce this issue with 4.3.0.0.beta1
Build ID: 2e39c7e59c8fc8b16a54c3d981dceef27fb0c07f4.3.0

which opens "Edit Fields".


4.1.6.2 opens "Input field" as described by João Mac-Cormick.
Comment 2 Caolán McNamara 2014-05-26 15:39:39 UTC
The old input fields were read-only so you had to double-click to get a dialog to change their value. The new ones are read-write so you just click on them (or cursor into them) and type to change their value. So now double clicking an input field is the same as e.g. double clicking a date/time field, the field dialog appears.

So, just click on it once and type the desired replacement text and it should "just work"
Comment 3 João Mac-Cormick 2014-05-28 13:44:55 UTC
Thank you.

I knew I could change it by clicking. However there was a change in behavior, so I reported it as a possible bug.
Comment 4 Friedmann Bruno 2014-08-19 09:32:20 UTC
I reopen this as a non functional UI BUG 
After deploying 4.3.0.4 we recieve a big number of complains after testing.

The fact that double-click was changed create a lot of confusion without any benefit for end user.

Here a list of the following trouble and inconsistencies found in last 4.3.0.4
(windows or linux have same behaviour)

In the attached model if you copy and paste a long text in address field.
And after that you want to change or two words, you can't double click on the word to select it. 
To be able to do a mouse selection you have to click on the field, then get out, then re click in the field, then you should be able to select a word or two.

Now the funny things (not from a end user point of view) if you use delete you can delete the selected word. But if you use backtab a warning dialog box is opened saying read only field can't be edited ... 
Then there's a complete confusion in user mind.

Now next point : using ctrl+shift+F9 is not a panacea, due to the fact that it restart editing field from 0 .. not the field you're on...
Take a few seconds and imagine a form that has 32 fields and at the end of your work, you want to edit the number 28 ??? You have to clic 28 time on next ...
Comment 5 Friedmann Bruno 2014-08-19 09:33:18 UTC
Created attachment 104878 [details]
Sample of form

use this form to follow the bug description
Comment 6 Owen Genat (retired) 2014-10-05 11:56:35 UTC
Summary edited for clarity. Note that if the essence of this report relates to editing input fields in protected sections, then bug 80806 is also related.
Comment 7 Joel Madero 2014-11-05 03:30:14 UTC
Closing this again - just because users haven't gotten used to a change does not mean it's a bug. A suggestion:

If you are truly convinced of this, bring it up to the UX mailing list and get them to look at it. Reopening a bug that has a clear explanation of the change is not going to move anything forward. Ping the UX mailing list - see their thoughts, if they are convinced it needs change, report a separate bug to change the behavior back. Again, please don't do this unless you can get wide acceptance from the UX team.