I just noticed this yesterday when testing a large layout, though I didn't take note of the exact point at which the slider bar glitched up. It doesn't seem to cause any functional difference to the layout itself though.

It depends on what version of node is shipped with the next stable...and I assume r189 will be the next stable.

Ashley:

Please let us use the previous version of node with r189...however it has to be managed.

—

Well, at least the last 2 or 3 versions. We can't expect Ashley to support every old version of node, but new versions seem to have a tendency to break things...

Canary is still nerfed, though not as bad as Chrome Stable (38). Chrome 38 even stutters slightly on the autorunner template...and that's on a 3570k after disabling scaling.

But the worst...is Firefox. I mean, it was never great, but it's become an absolute joke. Auto-runner is a slideshow...even as it reports 60 fps. How it got this messed up just boggles the mind.

IE is smooth as silk.

Ladies and gentlemen: welcome to the twilight zone.

I would like to be able to have more backup locations though; right now the limit is 3. I'd like to have C2 autobackup to 2 local drives and 2 cloud drives (dropbox and google drive). There are other ways to handle this of course, but it feels reassuring to set it all up in C2.

I think C2 should adopt a practice where it maintains compatibility with the last 2 or 3 versions of node. Default to the newest, but let us choose.