Created attachment 153449 [details] Sample DOCX with embedded Visio object Attached DOCX contains a simple Visio drawing (inside the zip it's word\embeddings\Microsoft_Visio_Drawing1.vsdx). When opened in Word and clicking on the object, it clearly behaves as an embedded object (upon double-clicking it'll complain if Visio isn't installed, that's expected). - Open and save it in Writer, then reopen in Word. => The object appears as a picture in Word (Picture tools ribbon shows on toolbar). The visio file is still there, but now it's word\embeddings\oleObject1.bin. Observed using LO 6.4.0.0.alpha0+ (d3d13140f0036c53aa74820b41acfeffa3572168), 5.0.0.5 / Windows 7. In 4.0.0.3 even the embedded file gets lost.
I think a good place to start is going to be reviewing https://cgit.freedesktop.org/libreoffice/core/commit/?id=d60398ff5b42ff77a4002dcd13b7fb8c9a73eade specifically +// TODO: this is probably a sub-optimal approach: ideally the media type +// of the stream from [Content_Types].xml should be stored somewhere for this +// purpose, but currently the media type of all OLE streams in the storage is +// just "application/vnd.sun.star.oleobject"
Created attachment 177495 [details] Extracted embedded vsdx Visio file
Created attachment 177498 [details] Resaved docx document with LO 7.4.0.0.alpha0+ Confirmed with build: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 4032284bf9629e9cfbbbb4597d0b10394f9e61be CPU threads: 8; OS: Mac OS X 10.16; UI render: Skia/Metal; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear Aron Budea, 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