To see the problem:
1. Open attachment 155996 [details]
2. Put some blank spaces after the field ("New value")
3. Edit the field (e.g. double-click and remove "New value" in dialog box, OK)
4. Place cursor somewhere else (e.g., end of file)
Result: The field becomes "invisible" (e.g., try to find it with a mouse click)
It can be found by moving the cursor (e.g., with the arrow key) until you land on it.
Expected result (enhancement request): To leave some kind of "trace" so that a user knows that the input field is present -- even if empty.
Think the usage is to use <Ctrl>+<F9>, or main menu View -> 'Field Names' which will toggle display of the Field Name and type or the string value of the field.
Example is "invisible" because when created you did not give it a Field Name, just the string value, which you'd then cleared.
But what has been annoying to me is that the Fields do not show in Navigator--nor record an object for movement via the Navigation toolbar.
Seems like they should, especially when they _are_ named.
(In reply to V Stuart Foote from comment #1)
> Think the usage is to use <Ctrl>+<F9>, or main menu View -> 'Field Names'
> which will toggle display of the Field Name and type or the string value of
> the field.
I understand. But in this particular use case, with an Input Field, it should be visible. Not dependent on Ctrl-F9.
> Example is "invisible" because when created you did not give it a Field
> Name, just the string value, which you'd then cleared.
This example was created by another person (with 220.127.116.11), which may explain why Ctrl-F9 does not work. (It does work with 18.104.22.168).
But where can one give a Field name in the Fields dialog?
Ctrl-F9 does not show field codes for Input Field variables created with a Text or User variable
Systematic procedure to see problem.
1. Create (and insert) a variable with Text format.
2. Create (and insert) a variable with General Format and alphabetic value
(e.g., abcd) (I know. But this is to illustrate a point.)
3. Create a User Field, with General Format and alphabetic value.
4. Insert three input fields, one with each variable.
- Text format variable is displayed
- General format variable displays (little) grey box
- User Field (with General format) shows alphabetic value
- Input field with Text and User displays text
- Input field with General displays (little) grey box.
Create and insert a User Field (with no value).
Note that a grey box is shown.
View > Field Names (Ctrl+F9)
- Input field with Text and User variables do not show field names
- All other fields display their contents (including the alphabetic values for the General Format variable)
1. Even though the input field with a General variable and the empty User Field does not show anything, the field itself is still shown with a grey box.
2. Similarly, Ctrl-F9 shows the codes for the General variable Input field box, but no field name codes are shown for the input boxes with Text and User variables.
3. As noted before, if you remove the contents (value) of the Text format or User format variables, then the Input box becomes invisible, unless you move the cursor until you "notice" that have have entered the field again.
Retested with LO 22.214.171.124 and same results with:
Version: 126.96.36.199.alpha0+ (x64)
Build ID: 444f0d256957544d26b9af9a0898364e829df1b
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win;
We have view > field shadings / ctrl+f8 to always identify fields (and some formatting marks). Speaking more generally you don't want to see fields but a kind of pixel-perfect print preview. And this variable input is rather a constant not meant to flexible enter data like done with form > text box, and other. So my take => WF.
(In reply to V Stuart Foote from comment #1)
> But what has been annoying to me is that the Fields do not show in
> Navigator--nor record an object for movement via the Navigation toolbar.
Absolutely, different topic though and I bet we have a ticket on this.
(In reply to Heiko Tietze from comment #4)
> We have view > field shadings / ctrl+f8 to always identify fields (and some
> formatting marks).
That would be fine with me, but in this case Ctrl-f8 does not show anything.
Created attachment 156961 [details]
Field highlighting with LibreOffice Still
(In reply to Heiko Tietze from comment #6)
> Created attachment 156961 [details]
> Field highlighting with LibreOffice Still
In your example:
1. Please double-click on "New value", which should open "Review Fields" dialog box.
2. Delete string "New value" (so that dialog box is empty).
Then you should be able to see the problem (i.e, the input field is not visible, and does not appear with ctrl+f8 or ctrl-f9).
Minimum width even for empty fields? Might be wanted to have zero width when empty.
Width should be zero, but it should have a field shading, similar as a soft hyphen has even a shading, when it is not at the end of a line and therefore not written.
If you go with the cursor over the input field using the arrow keys, you see a change in the cursor type, when you are inside the field. But that does not help, if you don't know, that there is an input field because there is no visual hint.
I support the request for a visible hint for empty input fields.
Created attachment 156963 [details]
simple illustration of user field
(In reply to Heiko Tietze from comment #8)
> Minimum width even for empty fields? Might be wanted to have zero width when
If this was a question for me...
...my only concern was to be able to see the field (e.g., with ctrl-f8)
...was not trying to propose enhancement or UX design.
If "zero width" has printing implications, then "zero width" might be preferred.
Simpled-minded illustration attached.
Created attachment 156964 [details]
(In reply to Regina Henschel from comment #9)
> Width should be zero, but it should have a field shading...
Exactly as it is implemented.
Created attachment 156968 [details]
screenshot of input fields
(In reply to Heiko Tietze from comment #11)
> Exactly as it is implemented.
For me, there is no field shading. I use Version: 188.8.131.52 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win;
Locale: de-DE (en_US); UI-Language: en-US
OpenGL is disabled.
In file it is an empty element <text:text-input text:description="Enter Text"/>
With content it is e.g <text:text-input text:description="Enter Text">inside</text:text-input>
Works for me with
Build ID: 6.2.8-3
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kde5;
Locale: de-DE (en_US.UTF-8); UI-Language: en-US
Build ID: ecb5130e16898c0d2485e99564c57882b5ef25b0
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3;
Locale: en-US (en_US.UTF-8); UI-Language: en-US
so likely a Windows issue. Let's treat it as an ordinary bug.
Modified summary to be more precise.
1. Only "Input Field" with no value becomes "invisible" (i.e. no shading, no toggle with Ctrl+F8 - (happens with Input Fields made with both "Variable" and "User Field")
2. If there is a value in the Input Field, then shading is shown (and toggled with Ctrl-F8)
3. If the value for the Input field is deleted (e.g., double-click on Input Field, use Review Fields dialog to remove text), then "invisible"
4. There is No Problem with a "valueless" User Field or a valueless Variable (e.g., in Text Format with no value) (i.e., shading is shown).
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://web.libera.chat/?settings=#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
(In reply to sdc.blanco from comment #14)
> 1. Only "Input Field" with no value becomes "invisible" (i.e. no shading,
> no toggle with Ctrl+F8 - (happens with Input Fields made with both
> "Variable" and "User Field")
Ctrl+F8 toggle now shows the empty input field, so closing as WORKSFORME
Version: 184.108.40.206.alpha0+ (x64) / LibreOffice Community
CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win