When printing iframe contents, svg images loded from file does not show up in print
Reported by
passi...@gmail.com,
Jun 10 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36 Steps to reproduce the problem: 1. open the test.html in Chrome 2. click on "Print" button 3. click on "Add svg" button, then click on "Print" button What is the expected behavior? That the printout matches the visible iframe document. What went wrong? The svg image that is loaded from file does not show up in the print. Did this work before? Yes Not sure Does this work in other browsers? Yes Chrome version: 67.0.3396.62 Channel: stable OS Version: Ubuntu 16.04.1 Flash Version:
,
Jun 11 2018
Able to reproduce the issue on reported chrome version stable 67.0.3396.62 and on latest chrome 69.0.3452.0 using Linux Ubuntu 17.10,Windows 10 & Mac 10.13.3. Same behavior is seen on M60(60.0.3112.113) hence considering it as non-regression and marking it as Untriaged. Thanks!
,
Jun 11 2018
Well I know for sure this used to work. It's just that I can not pinpoint the exact version where it stopped working.
,
Jun 13 2018
Do you remember roughly when it last worked? BTW, the "Add svg" button does not work in Chrome for me. It produces a JS error.
,
Jun 13 2018
Damn, I changed the id of the iframe element and did not update the addSVG function. Attached the updated version. It's also important that the html files are loaded in the browser via html (instead of opening it from file system), or Chrome will not let the host document access the framed document. I have a customer who used my JavaScript report library (that breaks because of this bug) on 29th of March. They might not had the latest version then, but definitely close. So the breaking changes happened some time between then and now.
,
Dec 14
Just tried this in 71.0.3578.98, and it works. I was working on a different bug.
,
Dec 14
Yes, I confirm this appears to be fixed in 70.0.3538.77 (Ubuntu 64bit).
,
Dec 14
Glad to hear it's fixed. Closing. |
|||
►
Sign in to add a comment |
|||
Comment 1 by krajshree@chromium.org
, Jun 11 2018