rotate(*deg) transformation causing blurring again (see #750433)
Reported by
schleckv...@gmail.com,
Jul 16
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: After the recent update the previously fixed bug (see #750433) came back. The behaviour is the same: Sometimes using of 'transform: rotate(*deg)' causes blurring; it seems the filter which usually is applied after rotation is done is not applied sometimes. What is the expected behavior? What went wrong? n/a Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: 10.0 Flash Version:
,
Jul 18
schleckviech@ - Thanks for filing the issue...!! Could you please provide a sample test file/url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Jul 18
krajshree, thanks for your fast answer! Could you please check this out? https://bit.ly/2utdV80
,
Jul 18
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 31
Tested the issue on chrome reported version# 67.0.3396.99 using Windows-10 with steps mentioned below: 1) Launched chrome reported version an d navigated to URL: https://bit.ly/2utdV80 2) Page got loaded and observed fonts are sharpen @Reporter:Please find the attached screencast for your reference, try to test this issue by creating new person with no apps and extensions in it or try to test this issue on latest chrome stable# 68.0.3440.75 and let us know if the issue still persists. You can download latest chrome stable fro URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
Jul 31
Nice, the issue seems to be fixed. There is no blurring now.
,
Jul 31
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 1
As per comment# 6 from the reporter, the issue is no more seen, hence closing it and marking it as Won't fix. Note: Feel free to raise a new one if the issue is seen again. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by vamshi.kommuri@chromium.org
, Jul 17