Beyond that, it doesn't even define the plugin API side of it, only the JS side. Defining the plugin API would make the proposal less bad (!= good) as then at l

Beyond that, it doesn't even define the plugin API side of it, only the JS side. Defining the plugin API would make the proposal less bad (!= good) as then at least the plugins wouldn't be browser specific (though I suspect quickly enough a de-facto standard will appear) I mean, at least something like NPAPI is (somewhat) documented, so that one can support all NPAPI plugins in any browser (say, Flash, Silverlight on OS X, etc.), even if what the plugins do themselves it totally undocumented…