Mike recently wrote a piece on Google's idea to kill the Google Chrome url bar in order to save up more space for websites and web applications (see Will Google Kill the URL Bar in Chrome?).
It appears that Google is not the only company that experiments in that direction. Mozilla's Paul Rouget published a screencast today that demonstrated some of his HTML5 and native control experiments.
What's the video about? It first shows how websites could add controls to the context menu of the browser. Examples are images that can be rotated or a new Twitter message dialog that can be launched that way.
That however was only the preparation for the second part of the demonstration where Paul showed how App tabs could utilize that feature and the previously mentioned Site Specific Browsers feature (see Firefox 5 Could Look Like This) to offer a new user experience.
Paul envisions different states for the browser, depending whether an app tab is active or a normal website. App tabs get rid of the url bar and make use of context menu controls and the new "site specific browsers" feature that is placed next to the Firefox button.
His idea basically is to give a webpage more control over the browser interface by giving it the means to "expose native controls to the UA", the context menu and, if it is a web app, options to get "rif of the URL / Back Forward Too bar".
Take a look at the video for a short demonstration, or visit Paul's blog directly for additional information.
Users who would like to try the experimental feature can download an experimental add-on from Paul's website.
Please note that this is just an experiment and not something that is planned to be integrated into one of the next versions of the Firefox web browser.
I personally think that it is not a good idea to give webpages or services control over the browser's context menu or user interface elements. Why? Because for the large percentage of sites that will make use of the feature in a positive way or ignore it, there will be minority of sites that abuse it if possible. Think of adding thousands of entries to the context menu (which could be easily prevented by setting a limit) or adding links or ads to it (which could be difficulty to prevent). Then there are security implications. Phishing websites for instance are easily identified by their web address. Removing the chance to verify the address removes the most reliable option of identifying phishing websites from the browser.
Another thought that came to mind is that the site specific browsers menu makes navigation more complicated. It may just be me but having two buttons open for a website, instead of one button seems to make things more complicated. I'm no user interface experts but would not it be better to integrate the "Site Specific Browsers" functionality right into the tab so that only one button is displayed for a website?
Please let me know what you think of the idea? Complicated or ingenious?Advertisement
Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.
We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.
If you like our content, and would like to help, please consider making a contribution:
Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.