Is it just me or does the homepage display noticeable lag when scrolling up/down? I'm assuming its due to the event handlers that trigger certain blocks' showing and hiding based on scroll position.
Works good with whatever the release version of firefox is as well (on osx). I've noticed for a while now that firefox has very smooth scrolling. Way better than both chrome and safari on my laptop.
If it wasn't obvious, some text and/or sections are clickable on that page; given that everything is "black" and looks alike, there is no delineation of interactive content.
Something is trying to be really fancy on the page, but I'm not sure it's worth a 200ms browser-paint event every step of a mouse scroll.
At least, this time, it mostly works in prominent mobile-browsers.
This site is almost a showcase of things not to do when designing a content site... inconsistent navigation, surprise interactivity, low contrast font/background combinations, inconsistent typography, icons thrown all over the place. I'm sure there's some useful stuff here, but I can't stand to decipher the navigation and focus on the text long enough to find out.
Lastly there is a unrelated display: box implemented by mozilla for XUL which is often confused with the flexbox standards but behaves in some weird ways. Ssee here:
http://csscurmudgeon.com/2011/11/flexbox-sucks/
Now we have an HTML5 advocacy site which is openly suggesting that people use the old webkit implementation and the unrelated mozilla spec based on XUL.
If anything, use the version in Chrome 17, its far better both in terms of property names and the flex() function.
I wasn't going to comment, as everyone else seems to have already commented how horrible this looks (and performs).
However, on closer inspection it looks like they've just tried to copy Windows Phone. There's the obvious big bold tiles, a generic enough idea that I wouldn't completely attribute it to Metro. However it starts to get suspiciously similar when you compare the mobile link in the top right of html5rocks with the more apps arrow to the right of WP7 start screen:
http://upload.wikimedia.org/wikipedia/en/5/55/Windows_Phone_...
27 comments
[ 581 ms ] story [ 2033 ms ] threadThe "Try this" demos on this page show features that Firefox supports, yet they only have "-webkit" prefixed styles so they don't work.
Is the page out of date? Many of the features have been supported since Firefox 4 according to their own browser support chart.
Something is trying to be really fancy on the page, but I'm not sure it's worth a 200ms browser-paint event every step of a mouse scroll.
At least, this time, it mostly works in prominent mobile-browsers.
The old standard which was implemented in previous versions of chrome and IE10 beta is here: http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/
Lastly there is a unrelated display: box implemented by mozilla for XUL which is often confused with the flexbox standards but behaves in some weird ways. Ssee here: http://csscurmudgeon.com/2011/11/flexbox-sucks/
Now we have an HTML5 advocacy site which is openly suggesting that people use the old webkit implementation and the unrelated mozilla spec based on XUL.
If anything, use the version in Chrome 17, its far better both in terms of property names and the flex() function.
The site has great content. The new design makes it too hard to read.
up up down down left right left right b a b a
Then you can shoot the whole site down.
However, on closer inspection it looks like they've just tried to copy Windows Phone. There's the obvious big bold tiles, a generic enough idea that I wouldn't completely attribute it to Metro. However it starts to get suspiciously similar when you compare the mobile link in the top right of html5rocks with the more apps arrow to the right of WP7 start screen: http://upload.wikimedia.org/wikipedia/en/5/55/Windows_Phone_...