(Angular/Chrome 70) Shadow text does not exit in dom
Reported by
tmburn...@gmail.com,
Nov 15
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Steps to reproduce the problem: This reported issue: https://github.com/swimlane/ngx-datatable/issues/1594#issuecomment-439199463 I think might be a larger Chrome issue. What is the expected behavior? What went wrong? The UI appears to copy elements into other elements ... they are rendered in the UI but in the debugger they dont exist. Did this work before? Yes Not 100% sure, but was only reported after chrome 70 Chrome version: 70.0.3538.102 Channel: stable OS Version: OS X 10.14.0 Flash Version:
,
Nov 16
,
Nov 16
Thanks for the issue... Tried to reproduce the issue on reported chrome 70.0.3538.102 using Mac 10.14.0. Attaching screencast for reference. Steps: ----- 1. Launched chrome 2. Navigated to given URL "https://github.com/swimlane/ngx-datatable/issues/1594#issuecomment-439199463" and opened "http://swimlane.github.io/ngx-datatable/#horz-vert-scrolling" 3. Scrolled up and down As we have observed that some rows gets highlighted with grey color but not seen ui glitches and background black @Reporter: Could you please check the attached screen cast and let us know if anything missed from our end Thanks..!
,
Nov 18
,
Nov 19
,
Nov 20
My original issue was here: https://github.com/swimlane/ngx-datatable/issues/1599 So i actually know how to reproduce this one better: Go here: http://swimlane.github.io/ngx-datatable/#row-details open a few rows, then collapse them. Then hover over rows that were opened and adjacent rows. Sometimes it will just flicker, other times it will stay. On my mac I only saw the duplicate data however on a Windows 10 i could see the black row (that was described in the other ticket). note: someone found a temp fix: https://github.com/swimlane/ngx-datatable/issues/1594#issuecomment-439379643 but it is odd that you would have to do this.
,
Nov 20
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
,
Nov 21
Able to reproduce issue on reported chrome version 70.0.3538.102 and not seen on latest chrome 72.0.3616.0 using Mac 10.14.0, Windows 10 and Ubuntu 17.10. Hence providing reverse bisect information below. Bisect Info: ================ Good build: 72.0.3610.0 Bad build: 72.0.3608.0 CHANGELOG URL: You are probably looking for a change made after 607304 (known good), but no later than 607305 (first known bad) https://chromium.googlesource.com/chromium/src/+log/3cb1d430ef07ac47baeca1ad607b870294ff06c1..ce731513c7fc60ee8953f98add4fe9a1e4e19563 suspect: https://chromium.googlesource.com/chromium/src/+/ce731513c7fc60ee8953f98add4fe9a1e4e19563 Reviewed-on: https://chromium-review.googlesource.com/c/1327158 Chris Harrelson@: Please confirm the issue and help in re-assigning if it is not related to your change. Thanks!
,
Nov 24
,
Nov 28
Chris - I dont have access to view 896716. I am fine closing this ticket if it is a duplicate, but can you provide me a synopsis of the findings of the other ticket? |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by manoranjanr@google.com
, Nov 15