weird CSS/GL artifacts when scrolling in Chrome 69 / Chromebook

[qmx]

it happens when I scroll on a thread on rust-lang zulip

Not sure how to provide more actionable debugging info, feel free to ask for more information.

[akashnimare]

@qmx Can you reproduce this on other tabs/websites? Also, does it happen frequently?

[qmx]

it happens exclusively in zulip, and happens so frequently that makes Zulip unusable :(

Any CSS styles that would trigger GPU rendering? I just need more directions on how to help debugging this...

[akashnimare]

Any CSS styles that would trigger GPU rendering?

Yeah, it's highly possible that some CSS style causing that issue. If we can reproduce this bug then surely we can fix it.

Some related discussion -

https://stackoverflow.com/questions/12502234/how-to-prevent-webkit-text-rendering-change-during-css-transition

https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-dev/eGYzE8l1D8c

The other thing you could do is to see whether this is reproducible on the desktop app, other browsers etc so that we can narrow down the cause behind this.

[qmx]

another data point, looks like it's related to the hovering that happens when you have your mouse pointer on top of the conversations while you scroll down.

[zulipbot]

Hello @zulip/server-browser-support, @zulip/server-message-view members, this issue was labeled with the "area: browser-support", "area: message view" labels, so you may want to check it out!

[timabbott]

Woah, I have never seen anything like this before. It's almost certainly a browser bug; Chrome 69 is new in the last week or so; hopefully Google upstream is going to fix this, but we probably can't count on that.

It is possible we might be able to do a CSS workaround for this. @qmx if you want to try using the Chrome inspector to disable CSS rules on the affected area until the glitch goes away, that's probably the best way to determine the root cause for this.

Also, does this affect everything in the organization, or just some messages? A link to a specific message that has this would be valuable.

[timabbott]

Closing this as never reproduced and likely fixed upstream by Chrome.