Bug 114566 - Saving document with form text boxes sets value in max text length property to taborder value FILESAVE FORMCONTROLS
Summary: Saving document with form text boxes sets value in max text length property t...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-19 19:01 UTC by Stuart Brown
Modified: 2017-12-26 19:06 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Brown 2017-12-19 19:01:58 UTC 
Description:
When I save a document that has a form with text boxes, the max text length of the text boxes defaults to the same number as the tab order value. Seems like a field is being written with the wrong property. I can explicitly change the max text length property and it will persist. But opening the document and editing again overwrites the with the tab order value.

Steps to Reproduce:
1. Create some form textbox controls - single line input
2. Don't set the max text length property, but set tab order property
3. save
4. close and re-open
5. max text length set to tab order

Actual Results:  
max text length set to tab order

Expected Results:
max text length should probably default to 0. If its set, it should stay set to that value.


Reproducible: Always


User Profile Reset: No



Additional Info:
Have not tried to use forms until now, so did not notice this before. 


User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Comment 1 Buovjaga 2017-12-26 16:01:15 UTC 
View - Toolbars - Form controls: Text box
Right-click - Control - General - Text type: Single line. Tab order: 7.

Max. text length stays 0 when I save and reload.

It might be that the bug was fixed after 5.1 was released, so please test with a newer version. A quick way is to use an AppImage: http://libreoffice.soluzioniopen.com/

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.

Arch Linux 64-bit
Version: 6.1.0.0.alpha0+
Build ID: 3272525e6b47af30ea5d92571cd7a6214117d359
CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group threaded
Built on December 25th 2017
Comment 2 Stuart Brown 2017-12-26 18:24:54 UTC 
Tried to reproduce in a simple test case using a new document in 5.1 so I would have something to test in 5.4 and could not. The original document was fairly complex and it would be difficult to narrow down the steps that led to the bug. Feel free to change the status of this bug to whatever is best for you. I am not going to work on it anymore unless it crops up again.
Comment 3 Buovjaga 2017-12-26 19:06:18 UTC 
Ok, thanks.