846272 (Closed, won't fix : do not agree, last attempt)
Reported by
edaa...@gmail.com,
May 30 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: I know comments probably won't get read when an incident is closed. I would advice you to read my further comments on the issue. https://bugs.chromium.org/p/chromium/issues/detail?id=846272#c6 The fact that other browsers do not have these render issues should ring the alarm. But clearly it didn't. I'm just trying to help and this is my last attempt. In the end I don't care, fix or no fix. The logical reasoning on why the blurring/gaps are fine do not change the fact: Transforms are inconsistent and therefor unrealiable for developers to use within Chrome. Im sure that eventually this issue will backfire a couple of times in the future before somebody will fix it. What is the expected behavior? What went wrong? View incident 846272 Did this work before? No Does this work in other browsers? Yes Chrome version: 66.0.3359.181 Channel: n/a OS Version: 10.0 Flash Version:
,
May 31 2018
,
May 31 2018
ccing dev eae@ and schenney@ for further inputs on this issue as per issue id: 846272. Thanks...!!
,
May 31 2018
Comments do get read when an issue is closed, we need to in order to know if it was incorrectly closed. Thanks for finding the duplicate issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by edaa...@gmail.com
, May 31 2018