TDD would've caught that. On Feb 8, 11:09 pm, mcot <[email protected]> wrote: > I've noticed this same thing with the NY times app on the chrome web > store. In my experience about 25-30% of the time it fails to load and > you get no content. I also notice this with the NY times app on the > apple app store which appears to just be a native app with a webkit > view hosting the same content as whats on the chrome web store. > > Its a difficult problem. While the idea of "progressive enhancement" > sounds nice, I can see it being particularly hard to achieve with > HTML5 web apps. Lifehacker is kind of a borderline case where they > really are not full blown web apps but include a lot of essential > functionality that needs JS. > > On Feb 8, 6:48 pm, cancel bubble <[email protected]> wrote: > > > > > > > > >http://isolani.co.uk/blog/javascript/BreakingTheWebWithHashBangs > > > "Lifehacker, along with every other Gawker property, experienced a lengthy > > site-outage on > > Monday<http://blogs.wsj.com/digits/2011/02/07/gawker-outage-causing-twitter-...>over > > a misbehaving piece of JavaScript. Gawker sites were reduced to being > > an empty homepage layout with zero > > content<http://dl.dropbox.com/u/3205568/lifehacker-loading-screenshot-2011020...>, > > functionality, ads, or even legal disclaimer wording. Every visitor coming > > through via Google bounced right back out, because all the content was > > missing. > > > Gawker, like Twitter before it, built their new site to be totally dependent > > on JavaScript, even down to the page URLs. The JavaScript failed to load, so > > no content appeared, and every URL on the page was broken."
-- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
