News:

BB code in posts seems to be working again!
I haven't turned on every single tag, so please let me know if there are any that are used/needed but not activated.

Main Menu

Disappearing arrowheads when printing an HTML page with SVG created by MS Visio

Started by Pradeep Pant, February 28, 2023, 11:34:38 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Pradeep Pant

Steps to reproduce:
Create an SVG file with a connector with arrowheads with MS-Visio 2016/2019 and the file is inserted into an HTML page with the tag.
The content of the HTML page (with included SVG) is displayed correctly in the browser itself (both Chrome and Edge).
But when this same HTML page is printed in the Chrome/Edge browser, the arrowheads do disappear (are distorted) in the print as soon the SVG file has been positioned on the 2nd page and/or further pages. The arrowheads are only printed correctly if the Visio SVG file is on the first page of the print of the HTML file.

Check the SOF link for sample code and example: https://stackoverflow.com/questions/75472125/disappearing-distorted-connector-arrowheads-when-printing-an-html-page-with-incl

You can see the print output of the sample code below:
https://imgur.com/a/ACLCELT

This buggy behavior is only with SVG files created with Visio and it is not present with SVG files created by similar diagram software (e.g. drawio  https://app.diagrams.net

Looking for suggestions to resolve this.

Thanks!

Nikolay

This has been answered on stackoverflow - it's a Chrome bug (fixed in Chrome DEV build now), not related to Visio.

Pradeep Pant

Thanks, Nikolay for your reply. As mentioned in my post I've already filed a bug with the chromium dev team but the bug is still open.
Can you please share the link to the chrome dev build so that I can test this?

You can check here
https://bugs.chromium.org/p/chromium/issues/detail?id=1417631&q=component%3ABlink%3ELayout%3EPrinting

Thanks again for your time!

Nikolay

Ah sorry my bad, I misread the stackoverflow issue, read "fixed" instead of "filed". I just thought you maybe did not check it for a long time :)

Pradeep Pant

No worries :-)
Today I've filed a bug with chrome also.
https://support.google.com/chrome/thread/204159586?hl=en

Let me know in case you get some pointers.

Thanks again for your time!

Browser ID: smf (possibly_robot)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 4: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 227 (show)
Files included: 32 - 1207KB. (show)
Memory used: 1043KB.
Tokens: post-login.
Cache hits: 13: 0.00160s for 26,767 bytes (show)
Cache misses: 2: (show)
Queries used: 15.

[Show Queries]