Bug 57363 - FILESAVE: MS Word Legacy form control content not saved when saving as HTML
Summary: FILESAVE: MS Word Legacy form control content not saved when saving as HTML
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.3.2 release
Hardware: Other All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: (X)HTML-Export
  Show dependency treegraph
 
Reported: 2012-11-21 10:48 UTC by lowds
Modified: 2024-05-24 03:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
MS DOCX file that can be used to reproduce the issue (22.18 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2012-11-21 10:48 UTC, lowds
Details
Sample HTML output of the Test.docx file (4.34 KB, text/html)
2012-11-21 10:49 UTC, lowds
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lowds 2012-11-21 10:48:36 UTC
Created attachment 70359 [details]
MS DOCX file that can be used to reproduce the issue

Problem description: 

Steps to reproduce:
1. Open a MS Word document (doc or docx) that contains legacy controls
2. See that the legacy controls (textbox, drop-down and checkbox) are populated with values from the saved file
3. Go to "File" > "Preview in Web Browser"

Current behavior:
The content of the legacy controls for drop-down and check boxes are not displayed within the HTML as they are not persisted.

Note that saving docx to doc will persist the control content, and the latest MS Word controls are fine.

Expected behavior:
The content of legacy controls should be shwn in HTML the same as the latest
controls are.  Note that they don't get lost if you save .docx to .doc file, just when viewing/saving as HTML.

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0
Comment 1 lowds 2012-11-21 10:49:31 UTC
Created attachment 70360 [details]
Sample HTML output of the Test.docx file
Comment 2 Florian Reisinger 2012-11-22 11:40:17 UTC
I can't see a difference between LibO 3.6.1.2 and Word 2010
Comment 3 A (Andy) 2013-04-19 21:18:51 UTC
reproducible with LO 4.0.2.2 (Win7 Home, 64bit)
Comment 4 QA Administrators 2015-03-04 02:23:33 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2015-03-24 17:07:39 UTC
Only dropdown and combobox are broken now.

Win 7 Pro 64-bit, LibO Version: 4.4.1.2
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Locale: fi_FI

Version: 4.5.0.0.alpha0+
Build ID: 181feb38d95e25980b96c2f6802cc906410abb13
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-03-19_23:38:28
Locale: fi_FI
Comment 6 tommy27 2016-04-16 07:25:43 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2017-05-22 13:27:30 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2020-05-23 03:43:14 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2022-05-24 03:33:31 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2024-05-24 03:17:25 UTC
Dear lowds,

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