MHTML (MIME HTML), a web page archive format introduced with Internet Explorer 5 and used to combine various images, animations along with the source code into a single (.mht) file, will be supported by the upcoming Google Chrome 14 release.
In fact, as of June 13th, Canary Chrome and WebKit builds already include such feature.
According to Wikipedia, MHTML file format is already supported by a few web browsers, including:
With the acceleration of the Firefox release cycle, Mozilla has released Firefox 5 Final ahead of the official release date that is June 21st.
Furthermore, with the release of Firefox 5 Final, you can expect to see the Firefox 6 Beta within two weeks.
According to the official changelog, the following version includes new web standards support, improves performance as well as memory usage and depending on how you look at it, no new usability features.
- Microsoft Labels WebGL A Fundamental, Unacceptable Security Risk
- Dangerous WebGL Flaws Haunt Chrome and Firefox
- Google Chrome Stable, Beta Channel Updates
- Google Chrome Beta Channel Update
- Offline Google Docs starts playing peek-a-boo
- Google bypasses admin controls with latest Chrome IE
- Chrome OS Beta Channel Update
- Apple iPad Safari users must pay to read New York Post
- Opera Allows Bookmark Sync With Windows Phone 7
- Facebook Is Taking A Special Interest In RockMelt’s Social Browser
- Deep Shot transfers open websites from desktop to mobile, sans wizardry
- Windows SkyDrive Says Sayonara To Silverlight, Embraces HTML5
Recently, Google has announced a couple of interesting new features for its search engine designed to enrich the overall experience.
The first one is called “Search by Image” which allows Google Chrome and Firefox (extension is required) users to search by using an image.
All you have to do is drag and drop the picture into the search box and that’s it, Google will figure out the rest (including location) and display somewhat relevant search results.
The future looks good.
There is some good news floating around about the future of web browsers. As of today, web browsers rely on native code plugins to display PDF files, like Adobe’s PDF reader or Foxit reader. However, this is about to change.
Fortunately for all of us, the web is quickly embracing the new technologies, and thanks to that, guys at pdf.js team plan to create a Firefox extension aka a built in PDF reader which uses HTML5 to render the documents.
As FavBrowser recently reported, there are ways to get around memory leaks in Firefox. Nevertheless, the problem appears to be serious enough for Mozilla itself to finally want to get it out of the way.
It’s become increasingly clear over the last several months that we have a pretty pressing need to deal with increases in memory usage in Firefox. Since we released Firefox 4 (and before, too), we’ve seen lots of reports about Firefox memory usage being higher than in older versions, and that Firefox memory usage is growing over time. – Johnny Stenback, a developer who works for Mozilla.
- Channel Switcher Dropped From Firefox
- How To “Fix” Firefox Memory Leaks
- Download Firefox 6 Aurora
- Download Google Chrome 12 Final
- French Exam? Use Google Chrome (Pic)
- Will It Blend? Chrome Notebook
- Apple Safari 5.1 Details
- Download Dolphin Browser HD 5.0 Final
- Nook Touch Web Browser
With Chrome OS notebooks already shipping, Firefox has also decided to join the party with the web browser based interface called Webian Shell, which is based on Mozilla Chromeless project.
As this is just an early and experimental release, the upcoming versions are set to incorporate more advanced features, such as: multiple home screens, split screen view, onscreen keyboard for touch based devices and more.
If you would like to try it out, here is a download link.
Going by what Mozilla has to say, the channel switcher will be removed from Firefox. Why? While the channel switcher seemed like a good idea at first, it was only really useful as a springboard it appears. This conclusion came to light due to the fact that the feature was rarely utilized once users made the switch to a particular channel.
As it turns out, users of Firefox are much more interested in running different versions of the browser alongside each other, and so Mozilla has declared that its efforts are best directed elsewhere. You will still be able to switch back and forth between the Aurora and Beta channels, of course. Simply visit the Future of Firefox page to obtain them.