(no title)
ianb | 12 years ago
Of course it's embedded in Firefox OS, but Firefox OS is really just Firefox built with special options, so in theory with some work you could expose that BrowserAPI to desktop. And there's actually a viable path whereby you could create a new browser as an open web app (https://developer.mozilla.org/en-US/docs/Web/Apps) with the permissions to use the BrowserAPI and it could be installed as a normal application, including on desktop. Of course that's a bunch of steps and unimplemented bits, but you'll be following a path that "upstream" is actually committed to. So committed they actually made just what you describe ;) (Even though the design of the browser is pretty conventional – but it's the concept of a browser-built-on-html that you are exploring at this point.)
spolu|12 years ago
Still really awesome. Thanks for sharing that. Are you involved with this?
ianb|12 years ago
The BrowserAPI is certainly not complete, but it's something. Some stuff might be harder than others. Intercepting networking is not very easy in Firefox – you can spy on networking, but the code isn't setup with hooks to change it up. And I don't know if something like localStorage would be exposed via the BrowserAPI – it's more low-level than that sort of thing. But if you are thinking about moving that kind of state around there's another Mozilla project called PiCL: https://wiki.mozilla.org/Identity/PiCL – it's working more in the guts of Firefox, but like much of Firefox it's in Javascript (compared to Chrome which is more biased towards C++). But it's not nearly as friendly an environment as content Javascript :( Anyway, that's more where localStorage manipulation and transportation is going to be happening in Firefox.
piranha|12 years ago