Why switch to Apollo to display HTML and dynamic content when a browser already allows it? Why use Joost Net TV to see if a browser already allows it?
Why has not the producer of two simple browser functions within them:
- Windowless windows
- P2P Object
Windowless windows
This simple feature would make the most of the HTTP connection and make it really useful browsers. To open windows (pop-up in practice) with only the title and no border, just in case in transparency, increase the production of widgets to be exploited with the normal browser, like what he does now Apollo . With a careful study on the safety (as I think it is now the only reason for this limit) would open up very interesting scenarios.
P2P Object
As we all know by now all browsers support the object XMLHttpRequest , which has given rise to an endless amount of so-called Ajax applications. This object can be accessed via JavaScript, is able to provide an HTTP channel - parallel - scriptable client for both IINV and receiving data.
Sooner or later, as anticipated in various other blog, Adobe will insert a P2P in Flash. Why not do the same thing in the browser? An object of this type together with Windowless features allow you to create applications like Joost-without installing anything on your machine, ensuring cross-compatibility worthy of the Internet, thereby increasing the efficiency of production (now Joost is developed for each system operational, which is quite heavy - both in money and time - in fact, the beta will follow ...).
RSS FEED short windows with text, audio and video from the place where we want on our desktops, in true W3C standards. Open TCP channels are directly from JavaScript, with endless possibilities of data exchange. Clearly, the will is little and the "crime" is high, hackers, spam and phishing are lurking and moves of this kind terrorize a bit 'all ...
Support and endorse. But Firefox 3.0 does not have anything like this?
FireFox has its own system - owner - identified with chromeless window! Even if what I meant was a little bit more evolved. The step, in my opinion, the W3C should do it of course ... otherwise we will continue to have the browser each with its own proprietary features and made it unusable!