Issue metadata
Sign in to add a comment
|
invisible text when rendered outside the viewport
Reported by
mohda1...@gmail.com,
Sep 30
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: I made this jsfiddle https://jsfiddle.net/muhamadfaifi/0no987fk/ to explain the issue. while you are in that jsfiddle do the following: 1. scroll down 2. click opacity: 1 3. click opacity: 0.6 4. click opacity: 1 5. scroll up 6. click opacity: 0.6 7. scroll down "you should see the text invisible again" What is the expected behavior? text is visible What went wrong? text is invisible Did this work before? N/A Does this work in other browsers? Yes Chrome version: 69.0.3497.100 Channel: stable OS Version: OS X 10.14.0 Flash Version:
,
Sep 30
Tested 69.0.3497.100 on both Linux and Mac. Could only reproduce on Mac. I'm guessing this is more likely closer to painting.
,
Oct 1
Works in M-71 Canary on Mac. mohda1415@, could you please install Chrome Canary and verify? A couple of opacity related issue have been fixed recently. Maybe this is one of them.
,
Oct 1
,
Oct 3
@schenney I received an update for canary today and it works, thanks. you can close this issue. don't worry about the video. it was an older version 71.0.3568.0 but in the latest one Version I currently have: 71.0.3569.0 works.
,
Oct 3
I think this was fixed by: https://chromium.googlesource.com/chromium/src/+/aa14bd3327d6d299d310f13fb900fdd636e30817 It would be great to verify with a bisect. @bug reporter, would you mind doing a bisect for us? It only takes a few minutes. https://www.chromium.org/developers/bisect-builds-py
,
Oct 3
Right now we can only bisect up to 595557, that is broken still. The fix patch is suspected to be 595576, so we'll need to wait a couple of days to bisect. Assigning to myself to bisect later in the week.
,
Oct 4
Able to reproduce the issue on reported version 69.0.3497.100 and the same is not seen on latest canary 71.0.3469.0 using MacBook Pro 10.13.3, hence providing reverse bisect info Reverse Bisect Info: ================ Last Bad build: 69.0.3568.0 First Good build: 69.0.3569.0 Unable to perform per-revision bisect as we are getting error on running it hence providing change-log from chromium bisect Change-Log: https://chromium.googlesource.com/chromium/src/+log/73a64c107201141b3af296e76fb8c98c14523d12..59aed3764077ffd201c04490e81801d6a24ed9f2 Suspecting: https://chromium.googlesource.com/chromium/src/+/aa14bd3327d6d299d310f13fb900fdd636e30817 from above change-log Change-Id: I650408cb3bc7c2b7fac932f7e968863bcdcd41d5 Reviewed-on: https://chromium-review.googlesource.com/1253063 @Chris Harrelson: Please confirm the issue and help in re-assigning if it is not related to your change, Please help in merging it to M-70 if applicable Adding ReleaseBlock-Stable for M-70, feel free to remove it if not applicable. Thanks!
,
Oct 4
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Sep 30