using LibO with Fedora 33, I'm having trouble with hyperlinks and SVG export. As soon as I add an hyperlink starting with "javascript:void(0);" to a graphic item (bitmap, shape, inserted svg, ...) this item is excluded from SVG export. I expected that it would be inserted in a <a id="whatever" xlink:href="javascript:void(0);"> markup surrounding the <g> that describes the graphic item. Steps to reproduce : insert 2 bitmaps/graphic items in a new document, insert a classical hyperlink to one of the bitmaps (eg : "https://bugs.documentfoundation.org"), insert a javascript call hyperlink to the other (eg : "javascript:void(0);"), export to SVG format : the resulting SVG file doesn't contain the 2nd item. My final goal is to promote using LibO-Draw to create SVG files presented/animated with Sozi and sounded with sonozise (see Sozi github discussions) to professionnal trainers that are not necesseraly very skilled with IT. The javascript links are there as very simple way to call a JS functions that play sounds during Sozi presentation.
Created attachment 172495 [details] example file example file containing 2 images (SVG import) - an owl - a tux tux has a hyperlink ("javascript:void(0);") When exporting to SVG and viewing with Firefox 88.0.1, tu x doesn't appear
To make my self clearer : I attached an example .odg file containing 2 images (SVG import) : an owl and a tux. I selected tux, added an hyperlink to it ("javascript:void(0);") and then exported the file to svg format. When I use Firefox 88.0.1 to display the resulting SVG, Tux doesn't appear. When I use Inkscape 1.0.2 to display the resulting SVG, Tux doesn't appear. HTH
Reproduced with document Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 67d8c245daf7c6ee33e908255f2bbd0ea8d08206 CPU threads: 2; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: fi-FI (fi_FI); UI: en-US Calc: threaded Jumbo Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 37613bffe4621c444e5a34678bafb2c3a875263d CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 26 April 2022
Dear Ned, 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