All posts tagged ‘firefox’

File Under: Browsers

Mozilla Building Metro Version of Firefox for Windows 8

Mozilla developers are planning to build a dramatically different version of Firefox for Windows 8, a change necessitated by Microsoft’s use of the touch-friendly “Metro” user interface for PCs and tablets.

Mozilla describes its Windows 8 plans as part of a 2012 Strategy & Roadmap document updated yesterday. A technology proof-of-concept demonstrating the feasibility of Firefox in Windows 8 is planned for the second quarter of this year, with timing dependent on the release of Microsoft’s Windows 8 consumer preview and developer documentation. A Metro version may be necessary for Firefox to avoid being shut out of Windows 8 tablets running on ARM, which will have only a limited “traditional” Windows desktop. But Mozilla is apparently planning Firefox builds both for the traditional Windows desktop environment and Metro.

“Windows 8 contains two application environments, ‘Classic’ and ‘Metro,’” Mozilla notes. “Classic is very similar to the Windows 7 environment at this time, it requires a simple evolution of the current Firefox Windows product. Metro is an entirely new environment and requires a new Firefox front end and system integration points.”

Metro Firefox will be a new Gecko-based browser focused on touch interactions, with both full-screen and partial-screen modes, with the possibility of a live tile so that users can see updates on the Start screen. There are several unanswered questions, such as which programming language to use for building the Metro front end. Firefox product manager Asa Dotzler further notes that “This proposal depends on Microsoft providing the same capabilities for Firefox as it does for IE—running at the Medium level integrity process that allows us the full use of the Win32 API and what we need from Metro, or a set of APIs that allow Mozilla to port Gecko to the WinRT. For the purposes of this feature proposal, I’m assuming we’ll get the first and we won’t have to port the bulk of Gecko and instead will use the win32 dlls from within Metro.”

Firefox accounts for about 20 percent of worldwide desktop browser market share, but has lost ground to Google Chrome over the past year. Chrome will presumably have a Metro version for Windows 8 as well, but Google has made no official announcement.

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.

File Under: Browsers

Mozilla Experiments With Fancier New Tab Page in Firefox 13

The proposed new tab page in Firefox 13

Mozilla is considering a fancier new tab page that will replace the current blank page presented when users create a new tab in Firefox. Like other browsers, Firefox will soon offer users a set of thumbnails on the new tab page with website recommendations based on the most frequently and recently visited pages in Firefox’s history.

If you’d like to see the new page in action you’ll need to download the Aurora channel build of Firefox. (Alternatively you can use the Nightly channel.) The new tab page will be enabled by default in Aurora until Feb. 16 for testing purposes. After that the feature will be hidden away while more work is done. Head over to Firefox Engineer Tim Taubert’s blog for details on how to re-enable the new tab page if you’d like to keep using it after that date.

The new tab page in Firefox looks similar to what you’ll find in Chrome and Opera. Indeed, every web browser’s new tab page is essentially a variation on what Opera pioneered with its “speed dial” page. The basic idea is to provide a quick way to access sites you frequently visit. Mozilla’s take thus far is to pull a mixture of your most frequently and most recently visited sites and display them in a 3-by-3 grid of thumbnails.

The goals for Firefox’s new tab page are ensuring that the page loads instantly, that it isn’t distracting and that it requires zero configuration. The latter explains why, thus far, the new tab features don’t offer much in the way of customization.

There are options to “pin” a site permanently to the grid, delete a site and rearrange the order of the sites. Each site will display a thumbnail once you’ve click on it. Or at least that’s the theory. As the screenshot above demonstrates there are clearly still some bugs in the screenshot feature.

The new tab page may be a little bit of a me-too feature at this point, but for those who have been wanting it, rest assured it’s coming. Firefox 13, which is when the fancier new tab page is slated to arrive is due in June 2012.

File Under: Browsers

Adobe Builds Flash Sandbox for Firefox

Flash logoAdobe wants to save Firefox users from falling victim to Flash-based security flaws. Working with Mozilla, Adobe has created a beta version of Flash with a new sandbox technology designed to limit the damage Flash-based attacks can do. Adobe previously added similar sandbox protection to Google’s Chrome browser.

If you’d like to test the new Flash Player Protected Mode for Firefox on Windows 7 or Vista, head over to the Adobe Labs download page. Bear in mind that this is a beta release and may contain some bugs.

The new sandbox feature for Flash in Firefox will provide extra protection against malicious browser exploits launched through the Flash Player. Sandboxing means that even when such attacks succeed, the damage is limited and won’t spill over into the rest of the browser or even the operating system.

The design of the Flash sandbox is similar to what Adobe uses in its Adobe Reader X Protected Mode. “Since its launch in November 2010, we have not seen a single successful exploit in the wild against Adobe Reader X,” writes Peleus Uhley, senior security researcher for Adobe. Uhley goes on to say that Adobe is hoping to “see similar results with the Flash Player sandbox for Firefox once the final version is released later this year.”

While Adobe has ceased development of mobile Flash, the company continues to develop and improve Flash for the desktop. HTML5′s canvas and video elements — among others — are designed to remove the need for plugins like Flash on the web. However, HTML5 support remains incomplete even in the newest browsers, and Flash will likely remain a necessary part of the web video and animation world for the foreseeable future.

File Under: Browsers

Firefox 10 Arrives With New Dev Tools and Full-Screen API

Mozilla has officially released Firefox 10. The new version of the open source web browser includes a handful of improvements and new features. The browser’s built-in tools for web developers got a particularly significant boost in this release. The new version also offers better support for a number of web standards.

Firefox’s developers decided last year to transition the browser to a time-based, six-week release cycle. The new release management strategy ensures that performance improvements and support for new web standards reach users as soon as possible. The faster release cycle posed challenges, however, for enterprise adopters and other users who require a longer support period. In order to address that issue, Mozilla has decided to offer an annual extended support release with a full year of updates. Firefox 10 is the first official extended support release.

A minor adjustment to the browser’s navigation bar is the biggest user-facing change in Firefox 10. The forward arrow button is no longer persistently visible by default in the navigation toolbar. It will only appear when the user navigates back a page. That means the button only shows when it can be activated. When the user clicks the forward arrow button and returns to the front of the history stack, the button will disappear again.

The distinctive keyhole shape that is formed by the back and forward buttons in Firefox’s navigation toolbar has been characterized in the past by Mozilla designers as an important part of the browser’s visual identity. Much like the angular tabs in Chrome, it’s an aesthetic characteristic that is uniform across platforms and helps make the browser recognizable.

The user interface change in Firefox 10 will make it so that the keyhole shape is only visible when the user navigates back. The feature worked predictably in our tests and didn’t pose any problems in practice. It’s worth noting, however, that it doesn’t appear to be available when the user has toggled the preference for small toolbar icons.

The new developer tools in Firefox 10

Another major change in Firefox 10 is the introduction of new developer tools. Previous versions of the browser have included a web console, a JavaScript scratchpad, and a simple tool for inspecting the Document Object Model (DOM). Firefox 10 has a new tightly-integrated developer panel with a richer DOM inspector and a tool for viewing, toggling, and modifying CSS properties.

The DOM inspector follows your cursor as you move it over elements of the page and will lock in on an element when you click. An HTML pane at the bottom of the screen will show you the markup for the target element and allow you to modify the values of element attributes. The HTML inspector pane also has a slick breadcrumb bar that makes it easy to see the position of the target element in the page hierarchy.

The CSS inspector will show you a list of CSS properties associated with the selected element, including inherited properties. Each one has a checkbox that you can click to toggle visibility. You can also click one of the values to replace it on the fly.

These built-in development tools in Firefox are simpler and less intrusive than more sophisticated alternatives such as the Firebug add-on. There are a number of additional features under development that will be included in the inspector panels in future versions of the web browser. One of the most intriguing is a tool that uses WebGL to show the user a three-dimensional representation of the page DOM. That feature wasn’t ready for inclusion in Firefox 10 and will potentially appear in the next major release.

In addition to the new inspector, web developers can also look forward to improved support for web standards. An addition of particular significance is a new full-screen API, which makes it possible for an individual HTML element to break out of the browser window and stretch itself to cover the entire screen. This feature is going to be especially useful for videos and games. You can see it in action by visiting Mozilla’s fullscreen demo page.

We first wrote about the full-screen API in November, when the feature originally landed in nightly builds. Mozilla carefully considered potential abuse scenarios when implementing the feature. It’s designed so that an element can only switch into fullscreen mode in response to a direct user action. The browser ensures this by using a technique similar to the one used to block unwanted popup windows.

Another addition in this release is support for 3D CSS transforms. This feature, which was originally created by Apple, offers a declarative mechanism for applying animated three dimensional transformations to individual HTML page elements. It’s important to note that 3D CSS transforms are entirely distinct from WebGL, which is a low-level JavaScript API for 3D programming.

Support for 3D CSS transformations is a welcome addition to the browser. Developers are already using the feature in the wild, but most of the existing 3D CSS content was authored with WebKit-specific prefixes and consequently won’t work in Firefox yet.

Firefox 10 is a solid release that expands the browser’s capabilities. Although the lineup of new features is slim, it’s a respectable update by the standards of the rapid release model. The new version will be pushed out through the Firefox update system shortly. Firefox 10 can also be downloaded directly from the Mozilla website. For more details, you can refer to the official release notes.

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.

Mozilla Demos MediaStream Processing, Audio Mixing in Firefox

Mozilla is drafting a proposal for a new web standard called MediaStream Processing that introduces JavaScript APIs for manipulating audio and video streams in real time. The specification is still at an early stage of development, but Mozilla has already started working on an implementation for testing purposes.

Mozilla’s Robert O’Callahan, the author of the MediaStream Processing API proposal draft, released experimental Firefox builds that include MediaStream Processing support. He has also published a set of demos (note: you need to run the experimental build to see the demos) that illustrate some of the functionality defined by the specification.

The demos show how the APIs can be used to perform tasks like rendering a visualization of a video’s audio track in a Canvas element while the video is playing. It also shows how the APIs can be used for mixing tasks, like implementing a cross-fade between two audio streams, dynamically adjusting the volume of a video, and programmatically generating audio streams.

One of the characteristics that distinguishes the MediaStream Processing API from previous web audio API proposals is that it aims to interoperate better with existing web standards. For example, it relies on the MediaStream interface in the WebRTC specification. It also allows users to take advantage of Web Workers for threading and will work with getUserMedia to eventually support real-time manipulation of streams from microphones and webcams.

The current implementation of the specification focuses on audio capabilities. As O’Callahan explained this week in a blog post, support for video manipulation will be added in the future when the necessary graphics APIs are accessible through Web Workers. MediaStream Processing on video will be useful for doing things like QR code recognition and augmented reality in web applications, he said.

Analyzing a video's audio track and visualizing it in real time

So, when will this functionality be available in a stable Firefox release? It might take some time. According to O’Callahan, the patch needs some cleanup before the functionality can land in trunk and make it into regular nightly builds. Even then, the MediaStream Processing functionality likely won’t be generally available until the specification has solidified.

“The biggest limitation is that it’s not shipping in Firefox yet. My giant patch is messy and a lot of cleanup needs to be done. I have a plan to split the patch up, clean up the pieces and land them piecemeal. In particular I need to get some of the infrastructure landed ASAP to help the WebRTC team make progress,” he wrote. “When we ship it, much or all of the API will probably be disabled by default, behind a hidden pref, until the standards situation is resolved.”

MediaStream Processing is definitely going to be worth the wait. Some fantastic capabilities are going to be unlocked when the specification is fully implemented. It will open the door for using native web standards to perform some sophisticated real-time media processing tasks that were previously only possible with browser plugins.

This article originally appeared on Ars Technica, Wired’s sister site for in-depth technology news.

File Under: Browsers

The Curious Case of Web Browser Names

Chances are your web browser is open all day, every day. Whether it’s Internet Explorer, Firefox, Opera, Chrome or Safari, the browser is the single most important piece of software most of us use. Given its central place in our lives, some history seems in order. If you’ve ever stopped browsing long enough to wonder why Safari is named Safari or where in the world the word “Mozilla” comes from, we have some answers for you.

Martin Beeby, a developer evangelist at Microsoft, has put together a nice little history of web browser names. Some are obvious — Internet Explorer came about because it was “a name that gave people a clear idea of what the product did” — some are less so, like Opera, which was apparently chosen because, among other things, “the Opera is fun.”

With the exception of Opera and IE, none of Beeby’s name origin stories come directly from the companies behind the browsers, so take all of these with a grain of salt. For instance, no one seems to know the exact origins of “Safari”, though the Beach Boys’ album seems like a reasonable guess — surfing the web, Surfin’ Safari… get it? The WebKit blog is named Surfin’ Safari, which might lend some credence to that story, but the name also nicely ties in with the notion of exploring the wild and connotes some of the same images as “explorer” and “navigator”.

Perhaps the least obvious name in the bunch is Firefox’s parent company Mozilla. Beeby cites a well-known story that the name that was derived by combining the words that were its original goal — “Mosaic Killer.” Webmonkey has heard another version of that story that claims the word “Godzilla” was the inspiration for “Mozilla,” a Godzilla-like force that would destroy Mosaic.

Beeby doesn’t offer any stories for less well-known browsers, like Konqueror, which, as the story goes, was going to “conquer” what IE and Netscape had “explored” and “navigated” respectively. The allusion didn’t really pan out, but, when Apple came along and ported KHTML to form WebKit, the developers did name their early efforts after a famous conqueror — Alexander.

For more details, and to learn where the names Firefox and Chrome come from, be sure to read through Beeby’s post.

File Under: Browsers, Programming

An Overview of Firefox’s Coming Developer Tools

Using the 3-D Page Inspector tool, coming soon to a Firefox near you.

Firefox is poised to deliver some new tools for web developers. When Firefox 10 is released in early 2012 it will add HTML and CSS inspectors designed to help web developers inspect and debug their code. Later releases will add more features, like a 3-D page inspector and even a built-in code editor.

Eventually Mozilla believes the built-in tools will replace the popular Firebug extension for most users, though it will likely be some time before that happens. In the meantime, if you’d like to see the new built-in developer panel in action, grab a copy of the Nightly builds, which all have the new tools in various stages of completion.

It’s worth noting from the start that these tools are not intended to replace the popular Firebug extension for those that need Firebug’s power user features. As Mozilla’s Kevin Dangoor wrote when the project was first announced: “we think Firebug is awesome… that’s why we invest so heavily in it already, more so than for any other add-on. We also want to explore new approaches to developer tools.” In other words devoted Firebug fans need not fret, the popular extension isn’t going away. The coming built-in developer tools are designed to supplement, not replace Firebug for the power user.

That said, the new developer tools will provide many of the basic features web developers require and will likely make Firebug unnecessary for many users.

Although they aren’t yet nicely integrated into a single panel like Firebug offers, by the time Firefox 12 hits prime time the browser will offer a web console, an element inspector with HTML and CSS info, Scratchpad for JavaScript development, a CSS style editor and an error console. Firefox’s view source will also add line numbers, closing a seven-year-old feature request.

The newest of these features is the page element inspector, which is now available in the beta channel. The basic layout of Firefox’s element inspector is a little different than what you’ll find in Chrome or Opera.

When you select “inspect element” Firefox will bring up a breadcrumb-style menu bar at the bottom of the page. To see the actual HTML or CSS applied to that element you need to click the corresponding buttons in the toolbar (or use the keyboard shortcuts). It’s an unusual design decision given that inspecting the element generally means seeing the HTML (at least that’s how every other browser does it), and it means there’s an extra click necessary to get to the same information that’s just one click away in WebKit and Opera.

The element inspector also dims out everything but the currently selected element — the visual opposite of what you’ll find in other browser’s inspectors, which color the currently selected element and leave the rest of the page as is. It’s not a deal breaker by any means, but it can be somewhat jarring when you’re used to opposite look.

On the plus side Mozilla has started work that will integrate the very handy Tilt add-on, which we reviewed a while back, into the inspect panel. The integrated Tilt option is only available in the Nightly channel at the moment, though of course you can just install the Tilt add-on if you want to use it today.

Look for the 3D inspector tools to arrive in Firefox 12 if all goes according to plan. Mozilla also plans to add a themeable Code Editor (so you can edit CSS files, or write JavaScript right in the browser).

While Firefox’s new developer tools are improving (and will be much more useful when the element inspector arrives in Firefox 10), there are still plenty of reasons to prefer Firebug or the WebKit tools. For example, if you open Firefox’s HTML inspector, style inspector and web console all at the same time there’s almost no screen space left for the actual page content. Firebug, WebKit and Opera all save considerable screen real estate by consolidating their tools into a single tabbed panel.

For more details on the new Page Inspector coming in Firefox 10, here’s Mozilla’s screencast overview:

File Under: Browsers

Why Google Continues to Fund Firefox

Just before the holiday weekend Mozilla announced that it had renewed its long-standing search revenue agreement with Google, which will reportedly net Mozilla $300 million a year (as part of a three-year contract). The renewed contract comprises the bulk of Mozilla’s funding and is unquestionably a good deal for Mozilla. What’s less immediately clear is why Google — which now has its own Chrome browser — would want to continue the deal.

Indeed, why fund the competition? M.G. Siegler speculates (based on AllThingsD’s report that there was a bidding war over Mozilla) that Google is willing to spend that kind of money just to keep Microsoft from starting a partnership with Mozilla.

That’s one theory. But it may well be that the truth is much more mundane. It may be that Mozilla is just one of a number of payouts that Google makes to help drive ad sales.

In fact, as Mozilla’s Asa Dotzler points out, Google pays out roughly 24 percent of its ad revenues to drive more traffic to its ads:

Not all traffic to Google ads is “organic” though. To help drive ad sales, Google pays for traffic to their ads. They paid out $2.21 billion, or 24% of their ad revenues in “Traffic Acquisition Costs”. That money goes to revenue shares with their AdSense partners and to “distribution partners” — presumably browser makers, PC OEMs, and mobile OEMs and operators.

As Dotzler goes on to point out Google pays out similar money to Opera and Apple, which both use Google as the default search engine in their respective browsers — again, driving eyeballs to Google ads. Dotzler’s point being that the Google-Mozilla deal is not a charitable arrangement, but a business deal built around driving eyeballs to Google ads. Firefox currently holds roughly 25 percent of the global browser market, which is certainly a healthy number of eyeballs..

Of course it’s possible that other factors may also influence Google’s decisions. Google Chrome developer Peter Kasting says that Google’s motivation for building Chrome is to “make the web advance as much and as quickly as possible.” That means, according to Kasting, that “it’s completely irrelevant to this goal whether Chrome actually gains tons of users or whether instead the web advances because the other browser vendors step up their game and produce far better browsers.” In other words, funding Firefox helps to further the same goal that drove the company to build Chrome in the first place — advancing the web.

That would be somewhat easier to swallow if other parts of the Google machine didn’t build so many experiments that only work in Chrome.

Regardless of Google’s motivation for building Chrome, or for funding Mozilla, both moves have proved great news for users. And in the end the precise motivation behind the Google-Mozilla deal are something only tech writers really care about. Users care about speed and there’s no question that Chrome has helped spawned a renaissance among web browsers and helped put speed back on top of every browser makers’ to-do list (the drive to adopt HTML5 has also done wonders to improve the average user’s experience on the web).

For most users the Mozilla-Google deal just means that there will continue to be a number of browsers to choose from and a number of browsers to help keep pushing the web, and each other, forward.

File Under: Browsers

Mozilla Unleashes Faster, Smaller Firefox 9

Mozilla has released Firefox 9, which brings speed improvements and uses less memory than previous releases. In fact, this release effectively puts Firefox back on a level playing field with Google Chrome when it comes to speed.

If you’d like to try out Firefox 9, head on over to the Mozilla downloads page. If you’re already using Firefox you’ll be automatically updated to version 9.

The big news in this release is under the hood where Firefox now supports what’s known as Type Inference. Type Inference is a new feature for Firefox’s SpiderMonkey JavaScript engine and means that complex JavaScript websites — which, let’s face it, is pretty much every website these days — should run faster. According to Mozilla, Firefox 9′s Type Inference should make the browser between 20 and 30 percent faster.

Alongside the faster JavaScript processing Firefox 9 continues to show improvements from Mozilla’s MemShrink project, an ongoing effort to reduce memory usage in the browser. Indeed, for the first time in a very long time my testing showed Firefox 9 using less memory than Opera (which has long been the least RAM-hungry browser I test). Opening the same dozen tabs in both Firefox and Opera used only 367MB of RAM in Firefox compared to 378MB in Opera 11.60 [Update: Note that the memory test was performed with the following Firefox add-ons running: AdBlock, Ghostery, BetterPrivacy and HTTPS-Everywhere.] There’s no longer much difference between the two, which is a testament to Firefox’s dramatic improvement over the last six months of MemShrink efforts.

Web developers get a few new toys in this release, including a fullscreen mode that allows any HTML element to take over the screen. Although fullscreen is primarily associated with video elements, there may be occasions (for example, HTML elements used in web-based games) where it makes sense to take over the screen. For now the fullscreen feature needs the -moz prefix to work.

Firefox 9 also includes a new “dim the lights” feature for HTML5 video. Dimming the lights means that Firefox will overlay the rest of the browser window with a gray background that let’s you focus on the video in question. Check out this demo video which shows the dimming in action.

While most of what’s new in Firefox 9 is under the hood, Mac users will notice a few cosmetic changes like a slightly tweaked look and feel that more closely matches the Mac OS X Lion toolbar styles. There’s also now support for two-finger swipe gestures to navigate back and forth in history (mirroring the same features in Chrome and Safari).

Firefox 9 is well worth the upgrade. If you moved away from Firefox due to speed problems and bloat this release warrants another look. Those plagued by the rapid release cycle’s habit of breaking add-ons may want to hold off, though. Firefox 9, for all its other improvements, may still break some add-ons. Mozilla has a solution to the breaking add-ons problem in the works, but it won’t arrive for another six weeks when Firefox 10 is released.

File Under: Browsers

End of an Era? Chrome Surpasses Firefox

For the first time Chrome Beats Firefox on Webmonkey.com

Once the darling of the tech set, Mozilla’s Firefox web browser is no longer the perennially #2 underdog of the web.

According to StatCounter, a web analytics company tracking browser market share, Google Chrome has overtaken Mozilla Firefox to become the second most used web browser in the world.

For the first time Chrome also managed to beat out Firefox to become the most used web browser among both Wired.com and Webmonkey.com readers.

StatCounter claims that for November 2011 Chrome accounted for 25.69 percent of browsers on the web while Firefox trailed it by the tiniest of margins at 25.23 percent. Both still pale in comparison to Internet Explorer’s 40.63 percent market share.

As Mark Twain noted there are lies, damn lies and statistics. StatCounter’s numbers should most definitely be taken with a grain of salt. NetMarketshare, which also tracks browser usage, still shows Firefox nearly four percent ahead of Chrome globally.

That said, the traffic split between Firefox and Chrome at both Wired.com and Webmonkey.com nearly mirrors StatCounter’s numbers. The main difference around here is that both browsers beat Internet Explorer. But for the first time in a very long time, Firefox is not the most used browser among Webmonkey readers. Last month Chrome accounted for 32.14 percent of users while Firefox trailed just behind at 31.06 percent.