The cake is not a lie.
With the release of Firefox 5, Microsoft’s IE team has decided to spoil Mozilla with a sweet surprise and sent them a cake.
As Firefox release cycle picks up the phase, we are wondering if the software giant will continue its delicious tradition.
Along with the release of Firefox 5 on Tuesday, Mozilla showed off the vulnerabilities that had been patched in that version of Firefox as well as in 2010′s Firefox 3.6, making no mention of any bugs fixed in Firefox 4, however. The reason for this is that Firefox 4 has reached its EOL, short for End of Life, with regard to vulnerability patches according to Mozilla.
Opera is a supporter of WebRTC as well.
Following Microsoft’s acquisition of Skype, it looks like the search giant has video chat plans of its own.
Turns out, Google is integrating its WebRTC software into the Google Chrome web browser, which will allow users to talk in real-time without having to install Skype or similar chat clients.
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.