Screen corruption, most browsers

[Shell (Aridhia Informatics)]

Hi guys,

Interesting one this. We're noticing some unusual screen corruption in most browsers in our branch of OC. We have some code that manipulates various views post-render. For example, our 'header' is a bar that can be hidden by the user to gain a little screen space. Our sidebars can also be hidden.

Using jquery to add and remove (and animate between) classes causes some rather odd screen repainting issues in Chrome and FireFox (Mac and Windows) - partially drawn borders, Bootstrapped tabs 'double drawing', torn/misplaced buttons and overlapping elements. Generally, after the painting problems, performing any action that causes a fresh repaint fixes most (but not all) of the display issues. Resizing the window fixes all the issues. According to Chrome's dev tools everything is where it *should* be.

I guess my query is along the lines of; have you guys ever seen anything along these lines? I can mitigate some of the painting problems by reducing the number of animated transitions and reordering, but it's rather... random.

S.

[Charles Hansen]

I've never seen anything like it.  Chorus does not use much animation.  One possibly related fact:  We have custom scrollbars which call setTimeout somewhat frequently to keep the scroll bars up to date.  In older versions of Chorus, there were sometimes leaks that caused the scrollbars to be bound repeatedly.  This would spam setTimeout so heavily that other animations (the toast messages) would be very choppy.  It might be possible that this is happening, though I don't know why it would cause the specific problem you have.  We diagnosed the problem by overwriting setTimeout to also have a console.log and just running the app.  It would print out thousands of times every time you did anything.  Not sure this would help, but good luck.

Charles

S.

--
You received this message because you are subscribed to the Google Groups "chorus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chorus-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Shell (Aridhia Informatics)]

Hi Charles, apologies meant to reply yesterday.

It could indeed be the scrollbars. We're merging Chorus 2.5 into our codebase and perhaps this will solve the issue. Regardless, we're looking to make more use of custom scroll panes in a future version of our product and maybe this is something we can look at as part of that. I'm trying to shift some of the composition out to the GPU too as a way to improve overall responsiveness.

Thanks,

S.