Nice idea. I’m hoping that we’re talking about apps using the elements and APIs discussed in the HTML5 spec, as opposed to just fancy JS stuff that people call HTML5 when it really isn’t. i.e. what happened with “DHTML” ...
Yes, you’re allowed to upload scripts with any version of jQuery, although we strongly recommend the latest (1.4.2). I’ve emailed the site manager about this issue. Thanks for letting us know.
I’m not sure if this is what you’re after but have you checked out Bespin? https://bespin.mozillalabs.com/
See this screenshot: http://bengalbraith.files.wordpress.com/2009/08/collab.png?w=680&h=551
I think I need to clear up a few misunderstandings here.
But, what we do expect, especially with items that offer content (and are not just decorative enhancements) is for the item to degrade gracefully – i.e. there should be some level of functionality when JS is disabled. This may be hard to grasp, but if you create something by progressively enhancing what’s already there then this becomes much easier.
We do let some items through that don’t degrade but these will typically be decorative enhancements that are not very important to the content of the site. For example, a Twitter widget that depends on JS is okay because the website does not depend on that content being there – it’s not absolutely necessary for the user to see those tweets – it’s just a contextual enhancement.
But, a navigation menu MUST degrade. Links/navigation are the core of the web. Adding these things via JS immediately locks out a bunch of important audiences – disabled users, security-aware corps that disable JS, search engine spiders… etc.
Depending on the quality and design of its implementation and other things like documentation and ease-of-use, I would say that this is up to the level of quality required (functionality-wise).
Great interview Jeffrey! And thanks for the plug!!