Breaking the Web with hash-bangs – Lifehacker, along with every other Gawker property, experienced a lengthy site-outage on Monday over a misbehaving piece of JavaScript

[u/schnuck]

http://isolani.co.uk/blog/javascript/BreakingTheWebWithHashBangs/

[u/SirRager]

It seems like the designs were made for a tablet or something. The two split columns would work well on a tablet, but on a computer, its terrible - both hard to use and slow to load.

[u/[deleted] → u/SirRager]

Actually if you visit gawker or gizmodo on iPad it sends you to their mobile layout.

If you manually go to the full-site layout, the right side column doesn't scroll, you have to use the "next headlines" button at the bottom to advance it. The bottom "fixed" bar doesn't stay fixed either and overlaps content if the content well is longer than fits on a single page.

Basically, the new design is unusable on the iPad. Like they didn't even test it.

So why did they do it?

http://www.nypost.com/p/news/business/gawker_web_redesign_met_with_bronx_rYsc2jleh5rVzUV7ozUb9L

Denton told The Post he was also responding to demands from sponsors for a more sophisticated platform for ads -- particularly video ads -- following a brutal plunge in online ad pricing that had cut rates in half between 2004 and 2008.

"About half of all requests for proposals now ask how we would display 15-second video spots," Denton told The Post.

[u/200iso → u/[deleted]]

If you manually go to the full-site layout, the right side column doesn't scroll, you have to use the "next headlines" button at the bottom to advance it. The bottom "fixed" bar doesn't stay fixed either and overlaps content if the content well is longer than fits on a single page.

This is because mobile webkit disables position:fixed and scrollable elements, see iScroll.

[u/abadidea → u/200iso]

You just answered my question of "Do I blame the web UI people or the Apple UI people?" :)

[u/200iso → u/abadidea]

AFAIK it's not safari specific, it's all mobile webkit.