ahrjay

Here's some interesting observations, this will work on any document that is in designMode or any element that has contenteditable attribute.

Firefox doesn't have the clipboardData interface like IE, Chrome and Safari have so it must be built into Firefox. From a quick look it seems like it doesn't expose the stream data to JavaScript which is unfortunate, I would love for this to be available.

This is fantastic, this mentoring network along with the startmate incubator will make for some great startups coming out Australia.

Yeah have seen that only issue is it's only for Opera browser. However Google[1] and Mozilla[2] are both working on remote debugging solutions that will allow you to have true remote debugging abilities, like attaching break points and do a whole bunch of really cool stuff that isn't possible with just JavaScript. There is also the weinre project[3] which has some huge potential.

[1] http://code.google.com/p/chromedevtools/wiki/ChromeDevToolsP... [2] http://getfirebug.com/wiki/index.php/Crossfire [3] http://pmuellr.github.com/weinre/

Memories indeed, I still have the 25 odd floppy disks needed to install windows 95!

Yeah good point should of had JavaScript in there. Sorry if you visited in the hopes of some terminal tips.

Considering chrome and firefox are switching off websockets until they resolve the security issues that wouldn't be very viable. I guess you could fallback to flash sockets or long polling.

They didn't "switch it off" they merely turned off form submission blocking when the form was invalid. It's back on in chrome now because they have the error notification bubble. The constraint validition API, the error pseudo-classes and the extra attributes all work in Safari.

I do hate when people don't even bother to read the article.

It's 1.5kb of CSS that doesn't require any javascript.

I would be interested to know which browsers it's broken in? IE8 and below don't support the :checked pseudo-class, the fallback is to show the list fully expanded. Otherwise the browser support is quite broad.

I think the single folder is that killer feature that certainly won them the market share. It's entry point is incredibly simple yet for the more technically inclined we can simply setup symbolic links to create the multi folder functionality.

His code uses an invalid technique that go against the spec[1]. You cannot add generated content to a replaced element IE8 and Mozilla follow the spec, webkit and Opera don't. It's a shame that this is the case.

[1]http://www.w3.org/TR/css3-content/#replacedContent

If by badass you mean horrible, then yes. It browser sniffs and then adds classes to the html element depending on which rendering engine, version and platform you're using. e.g. in FF 3.6 the html element has "mozilla windows v3 v3-6".

The whole Drag and Drop API started life as a Microsoft only API. It's certainly not a bad thing that the Chromium team went ahead and did this, it's how innovation happens. Someone needs to take the first step.

The File API was the same, Mozilla went ahead and added it to Firefox and now it's in Chrome and soon other browsers will follow.

Ah thanks for that, it slipped by my proof reading.

Yeah I thought about adding in some css transitions for safari 4 but went against it due to it causing problems with every other browser that doesn't support the -webkit-transition property.

Good theory I would be very interested to see your results.