Created attachment 122959 [details] An ODT with 3 images: embedded, linked & "data URL" (last one is not shown) LibreOffice Writer allows the user to especify an image by means of a URL. If an HTTP URL is used, things go fine (if the link isn't broken), but LOWriter fails to handle DATA URLs properly. In the attached document, the 3rd image is not shown as it should. Tested versions: 1) Version 3.5.7.2 on Ubuntu Linux. 2) Version 4.1.5.3 on Windows 7 Professional 64 bits. In cases 1 & 2, LOWriter suffers when having to try to render the image: everything slows down unacceptably. And the image is never shown. 3) Version 4.4.7.2 on Windows 7 Enterprise 64 bits. In case 3, LOWriter shows the message “inline image” instead of the image itself, but “without pain”.
How do you specify the image by means of an URI in Writer? I opened the odt as zip, went into content.xml and copied the data:uri to an html file. When I opened the html file in a browser, selected the image (the head of some dude), I could paste it into writer just fine. One question is, why would you want to use a data:uri type of image in writer? Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
> How do you specify the image by means of an URI in Writer? 1. Get a DATA URL from the image here: http://dataurl.net/#dataurlmaker. 2. Insert any image in the doc. 3. Access the dialogs associated with this image and paste the DATA URL as the image link/filename. > I opened the odt as zip, went into content.xml and copied the data:uri to an html file. When I opened the html file in a browser, selected the image (the head of some dude), I could paste it into writer just fine. > One question is, why would you want to use a data:uri type of image in writer? I think that's not the question, but: how do you think LOWriter should react if the URL for an image belongs to the DATA type? If you think the correct answer is "not showing the image, because the ODT creator should have chosen a different way for specifying that image", just reject the bug report. You can find how I ended up writing this bug report here: http://en.libreofficeforum.org/node/12614
Hi Fede, Yes 3.3 to 4.1 would max out a cpu core as it attempted to process it, while 4.2 and 4.3 would have a "read-error message" on the blank image. 4.4 and above have the "inline image" on the blank image, but opening the image properties dialog would show the preview of the image that wasnt rendered in the document. So as we are rendering it in the dialog, it should be rendered in the document as well, just like we do so for data url images in writer web.
** 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
Dear Fede, 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
Dear Fede, 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