New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 770032 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

SVG appearing outside IMG bounds when printed

Reported by inexorab...@gmail.com, Sep 29 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Save the files locally
2. Open booklet.html
3. Observe that the image is contained in its bounding box
4. Print - make sure Save as PDF is selected

What is the expected behavior?
Print matches screen - the image is contained in its bounding box

What went wrong?
Parts of the SVG image which are clipped within the SVG itself - and occur outside the image bounds - appear outside the bounding box of the image.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 61.0.3163.100  Channel: stable
OS Version: OS X 10.12.6
Flash Version:
 
booklet.html
165 bytes View Download
villis.svg
54.8 KB Download
Labels: Needs-Triage-M61
Cc: ranjitkan@chromium.org
Labels: -Type-Bug -Pri-2 hasbisect-per-revision M-63 OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: bsalomon@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Windows 10, Mac 10.12.6, Ubuntu 14.04. Issue is a regression broken in M55 builds. Below are the bisect details for the same:

Bisect Info:
============
55.0.2879.0 - Good Build
55.0.2880.0 - Bad Build

Change Log: https://chromium.googlesource.com/chromium/src/+log/3186773510907edfda53bf8fef382a087f61c6f4..e385b0636d1295f643c7e32e28e396b990067318

From the third party roll: https://chromium.googlesource.com/skia.git/+log/7de577983581..2ebd0c80a2a9 suspecting below change could be a possible culprit:

https://chromium.googlesource.com/skia.git/+/0f147ac2ae575bbad3515a526f13700bc5c8e9d7

@ bsalomon: Assigning to you, request you to please take a look into it. Please help us to find an owner if not with respect to your change.

Thanks.!


Comment 3 by f...@opera.com, Sep 29 2017

Components: Internals>Skia>PDF
Cc: jsb...@chromium.org
FYI the reporter is me in my non-work identity; let me know if I can help out! Just don't assign to me since I'm clueless about the rendering side of Blink

Interestingly, a similar bug appears to manifest in other browers; I'm assuming it's just a lack of test coverage since I can't fathom that the behavior is intentional.


Given that it's a clipping issue, https://chromium.googlesource.com/skia.git/+/a3b45d4f7db953472df4f11ab1595964b65175f9 looks like a more likely culprit, but again I'm clueless about pushing pixels around.
Has anyone found any sort of workaround for this? Printing SVGs out of chrome is a significant feature on one of our tools and this has hit us pretty hard. We have some machines running old versions, but that is the only thing we can think of right now.
Components: -Blink>SVG
Labels: -Pri-1 -Type-Bug-Regression -Needs-Triage-M61 Pri-2 Type-Bug
Not a regression for tracking purposes because it happened back in 55.
Has there been any update on this at all? Is it still on someone's radar?
Status: Started (was: Assigned)
Sorry for letting this lie for so long. Taking a look.
Cc: halcanary@chromium.org
print.mskp
794 KB Download
Simplified test case attached


crbug_770032.html
535 bytes View Download
Status: Fixed (was: Started)
I think this may be 772685, so marking as fixed.
Tried this on tip-of-tree. With the original repro case: rather than not being clipped (original bug), potentially clipped elements are simply missing. They reappear in print preview if print settings are changed to Landscape or Tabloid mode.

Once I'm back on a desktop machine I'll try and bisect since it could be a separate issue, not a bad fix, but something is still very wrong with clipping. :(



Yeah, this is still busted, just in a different way. Instead of elements being clipped they simply disappear. :(

I filed a new bug:  issue 837279 

Sign in to add a comment