The site has some issues on tablets, simply as the scroll event doesn’t fire until you stop scrolling, and so the animations don’t trigger continuously like they do on desktop browsers, only when you stop scrolling. It didn’t crash when I tested it though.
Unfortunately, as it’s a side project, I didn’t have time to rectify this (using iScroll or something similar). Would like to find a solution though.
Thanks :) Think it's easy for some to forget it's a tech demo, so it isn't meant to be absolutely 'perfect', but really happy with the feedback so far.
Good idea re the curtain - it would be quite an easy port to make the animation work like that, so think I might do that at some point.
Think there are lots of possibilities around window resizing that haven't been explored yet - could make some really interesting effects...
Not a dumb question - only reason was because I wanted an excuse to play around with css animations and see how powerful they are in their current state.
SVG would probably be much more robust as a solution (as would canvas have been) - I think the demo shows more than anything that CSS3 animations need slightly more reliable support across modern browsers before they are a viable choice for doing some really nice things with them.
Thanks for the feedback - reason it's a bit buggy is mainly down to the implementation of the animation step-timing.
In Firefox, it works as you would expect, stepping through the spriting. In webkit, it's very inconsistent in how it renders, and doesn't look as polished because of this.
I've noticed the speed of the animation being effected by the resizing - like mentioned to others, will probably release a version which just shows the animations off separate to the window resizing as well to avoid this. The main reason for including reliance on media queries was to fit it into the mozilla dev derby criteria for this month.
Decent point on not knowing how big your window size is - think I'll update to include a width counter on the start screen.
Reason for the resizing down at the start is simply so only certain parts of the animation show at different times. It means I can control what width the animation is being viewed at, as otherwise I'd have to animate everything across a very large width potentially, which would be pretty time consuming, as this could be huge. Think with the feedback I've had, will release as a non media query animation as well when I get chance.
It took me a while to realize that the resizing was the whole point -- the scene animates as it gets wider.
There's nothing ground-breaking here, but neither is there in many of the XKCD stunts that we fawn over here. I think if you just describe it that way we'd all know what's going on.
It seems the minimum reported by window.innerWidth on 16.0.2 (OS X, 10.8.2) is 453. Once it hits that, I can drag it all the smaller I like, and it is stuck at 453.
I explored a few options - the reason I decided to make it controlled by the user was so it didn't have to open in a new window (as you can only control the width of the window with JS in a separate window).
Thanks for the feedback though - might create a separate self-running version at some point.
This only works when resizing the window? Would an ever-increasing div work? If you floated it right the size would always increase on the left, mimicking the drag and resize action that the user is doing.
That said, I get that you're pushing the limits as it is here and you've likely already considered this as an option.
This could be something I look to include next year though if there’s interest in finding out about usage.