Rotated image not displayed correctly
Reported by
sc...@photolynx.com,
Dec 20 2017
|
|||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Steps to reproduce the problem: 1) Look at https://jsfiddle.net/daneren2005/ca0rovs3/112/ 2) Add rotation and a bunch of drop-shadow to an image. This is a bit tricky to reproduce. If you change the img width/height from a percentage to an absolute pixel number it will stop breaking. In my website with much more stuff going on it is broken with % sizing though. On my site it also only breaks on some image/rotation combinations (though I could not find a common cause between them). If you take off the drop-shadow from the inner div it will render fine. If you take off the rotation it will render fine. The work around I found was to apply `backface-visibility: hidden` to the outer element. Unless I am misunderstanding the property this should not be making more of the element visible like this. What is the expected behavior? It should show the full image What went wrong? Only a part of the image is displayed. In other browsers it displays the full image. Did this work before? N/A Chrome version: 63.0.3239.108 Channel: stable OS Version: 10.0 Flash Version: Using Windows 10 with a normal install of Chrome with nothing special installed that I am aware of. I've had multiple customers contact me about this same issue so I don't think it is isolated to one OS/hardware configuration.
,
Dec 21 2017
Unable to reproduce this issue on reported version 63.0.3239.108 using windows 10 with steps mentioned below. Attaching screencast for reference. 1.Navigated to https://jsfiddle.net/daneren2005/ca0rovs3/112/ and observed image. 2. Now removed /* */ for outer element and clicked RUN 3. Observing image same as before. i.e; Entire image is seen without any chop. @Reporter: Please check the video and let us know if we miss anything. If possible please guide us with a video. This would help in further triaging of the issue. Thanks!
,
Dec 21 2017
Here is a screenshot. I'm not really sure if a video will add any more information since it would just be a video of me opening the jsfiddle. I'm not really sure what other info I could give to help reproduce. Is there anything else you can think of which would help?
,
Dec 21 2017
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 22 2017
Able to reproduce this issue on reporte version 63.0.3239.108 but fixed on latest beta 64.0.3282.39 and on latest canary 65.0.3301.0 using Windows 10 and Mac 10.13.1 with steps mentioned in comment#0. Hence providing reverse bisect info. Observations: =========== 1. Issue is not reproducible on Ubuntu 14.04 2. Issue is not reproducible on Windows10 Surface Pro Last Bad Build: 64.0.3279.0 First Good Build: 64.0.3280.0 CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/b4c579cc9e9c123839a0674bda83b4a91276c905..04f4824dd3e9ff81d39072d83daecee65a4b9781 Skia Roll:https://skia.googlesource.com/skia.git/+log/12b69eedeed5..0f8e4dbd28d1 Probably fixed by https://skia-review.googlesource.com/76802 @reed: Please confirm whether this is safe to merge to M-63. Adding RB-Stable for M63. Please remove if not the case. Thanks!
,
Dec 22 2017
,
Dec 22 2017
Yep, it should be safe and easy to merge this to M63. 399def9 remove clip-bounds query overrides from SkColorSpaceXformCanvas
,
Jan 2 2018
mtklein@ want to check since the issue doesn't reproduce on M64 and above can we live with this for M63, Since M64 would hit stable on Jan-23rd(if all go's well) since at this point we don't have any plans can we live with this for next 3 weeks. Please correct me if I am not accessing the impact of the bug.
,
Jan 2 2018
There is a work around so I am fine with waiting until 1/23 for the fix release. Obviously I am not the only one affected by this, but no one else has reported it yet so hopefully the impact is fairly small. Just my 2 cents.
,
Jan 9 2018
,
Jan 9 2018
This fix has missed the M63 train. M64 goes stable in 3 weeks. Also it's not a stable regression, as the current stable versions that are live already have the bug.
,
Jan 9 2018
Let's close this bug then. Mike?
,
Jan 9 2018
Oh, yep, sorry, I think pbommana@ and I decided to do that last week over chat, but I never got back around to close of the bug.
,
Jan 9 2018
[Auto-generated comment by a script] We noticed that this issue is targeted for M-64; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-64 label, otherwise remove Merge-TBD label. Thanks.
,
Jan 10 2018
Per comments above, doesn't seem like a merge is required. Removing Merge-TBD |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by sc...@photolynx.com
, Dec 20 2017101 KB
101 KB View Download
37.1 KB
37.1 KB View Download