Created attachment 70810 [details] A document created with MS Word with a single field with default text as TEST and help text as <?TEST?>. Opening in LibreOffice and saving causes the field to be removed. Problem description: I can create a RTF document with MS Word (2010), with a legacy text form field (accessed through the developer toolbar -> controls -> legacy tools -> text form field), and save it as RTF format. When I open this document in LibreOffice, this field doesn't seem to persist (based on not being able to access the field properties and the field being lost are saving the document in LibreOffice). Is there a good way to handle RTF documents with form text fields? (I also tried creating a document in LibreOffice with a form formatted field, but it also doesnt persist after saving as RTF). Steps to reproduce: 1. Create RTF document in MS Word with a legacy text form field 2. Open document in LibreOffice 3. Make some changes 3. Save document Current behavior: Form text field is lost after saving the document in LibreOffice Expected behavior: The form field should persist after saving in LibreOffice. Ideally, the ability to create these fields in a document from LibreOffice. Operating System: Windows 7
Unsure what to make of this. When opening the test document with LO 4.3 latest nightly or MS Word all I see is the word test. I'm unable to spot any differences in the way this is displayed. Is this bug still valid / reproducible with the latest LO release? Currently 4.1.3.2: http://www.libreoffice.org/download/ Could you please attach the document in question? That would help speed up the process of confirming and successively fixing this bug a lot. Thanks :) Setting to NEEDINFO until more detail is provided. After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :)
Created attachment 95635 [details] RTF file with form field created in MS Word
@Foss, Should have provided the original file (with the form field) as a comparison. Here's the file with the field, created in MS Word. Just to summarise: When opening the file in LibreOffice, saving some changes, the form fields are lost - the text is still there, but it is no longer a form field. At the time of the original bug report, it was version 4.0.4.2, I've just tested this with the latest version: 4.2.1.1, and it still behaves as described.
Still repro with LO 6.0 daily build (2017-09-22_22:54:52, 0db08432c69adc36ed464c1f7c8e672acb3752d) / Windows 7.
** 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! Warm Regards, QA Team MassPing-UntouchedBug
still repro in Version: 6.2.0.0.alpha0+ Build ID: 1aa37aa6bee19099b57555a6d839992b054aa405 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-09-23_10:17:54 Locale: ru-RU (ru_RU); Calc: threaded
Dear trent.schafer, 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! Warm Regards, QA Team MassPing-UntouchedBug
Confirm the issue is still present. Tested on latest version grabbed from website Version: 6.3.2.2 Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Dear trent.schafer, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Created attachment 177732 [details] The second file saved in current master, opened in MSO Now the field is exported back to RTF as field, however it's a bit broken according to MSO. Double clicking on the field brings up a Properties dialog with the original attachment 95635 [details] but after LO roundtrip MSO says: This command is unavailable because the form field was not inserted with the Forms toolbar or by using the Insert Form Field dialog box. Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4a388f5e01ebb5a512931d11e48c4380382239c8 CPU threads: 13; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded
Created attachment 177733 [details] The fields Text Form Field Options dialog of the original example file in Word 2010
Created attachment 177734 [details] RTF Bookmarks in Writer after resaving the file a few times Another slight issue is that MSO defines a bookmark "Text1" for this form field, as seen on the previous screenshot. When saving the example file as RTF then re-saving it again, this bookmark multiplies so each save adds one extra bookmark to the file. This may or may not be the cause of the Word error message on my firs screenshot.
The field started to be saved in 6.4.0 with the issues above.
Dear trent.schafer, 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! Warm Regards, QA Team MassPing-UntouchedBug