Trailrunner7 writes "Yahoo on Wednesday launched a new browser called Axis and researchers immediately discovered that the company had mistakenly included its private signing key in the source file, a serious error that would allow an attacker to create a malicious, signed extension for a browser that the browser will then treat as authentic. The mistake was discovered on Wednesday, soon after Yahoo had launched Axis, which is both a standalone browser for mobile devices as well as an extension for Firefox, Chrome, Safari and Internet Explorer. ... Within hours of the Axis launch, a writer and hacker named Nik Cubrilovic had noticed that the source file for the Axis Chrome extension included the private PGP key that Yahoo used to sign the file. That key is what the Chrome browser would look for in order to ensure that the extension is legitimate and authentic, and so it should never be disclosed publicly."

markjhood2003 writes "Fresh on the heels of Slashdot's discussion of the lack of browser choice on mobile devices comes the announcement of Yahoo's new web browser Axis. According to VentureBeat, the browser runs on iPad and iPhone as a separate standalone browser and as an extension for Chrome, Firefox, and Safari, with support for Android and Windows Phone coming soon. It actually appears to bring some innovation to mobile search, displaying results and queries on the same page for more productive navigation between the two."

bonch writes "Chrome was recently called the world's no.1 browser, but Microsoft is accusing the source, StatCounter, of using flawed methodology. When a user enters a search in Chrome, the browser preloads an invisible tab not shown to the user, and these were being counted by StatCounter. Net Applications, another usage tracking group, ignores these invisible tabs and reports IE at 54%, Firefox at 20.20%, and Chrome at 18.85%." Whereas the saturation of MSIE is totally organic, right?

redletterdave writes "Just six months after Google Chrome eclipsed Mozilla's Firefox to become the world's second most popular Web browser, Chrome finally surpassed Microsoft's Internet Explorer on Sunday to become the most-used Web browser in the world, according to Statcounter. Since May 2011, Internet Explorer's global market share has been steadily decreasing from 43.9 percent to 31.4 percent of all worldwide users. In that time, Chrome has climbed from below 20 percent to nearly 32 percent of the market share. Yet, while Chrome is now the No. 1 browser in the world, it still lags behind Internet Explorer here in the U.S., but that will soon change. Chrome currently has 27.1 percent of the U.S. market share, compared to Internet Explorer's 30.9 percent, but IE is seeing significant drop-offs in usage while Chrome continues to rise."

Mozilla has announced the availability of a new beta version of Firefox for Android. The release notes list many of the new features and fixes, which include Flash support, improvements to panning and zooming, plugins loading only on touch, and a new "Awesome Screen." They point out that many Android phones are supported, and that a beta version for tablets will be coming soon. Mozilla is asking for help "testing everything from the faster startup and response times to compatibility for specific websites and graphics performance." Here's the download page.

An anonymous reader writes "Last week we heard complaints from Mozilla that Windows RT would restrict users' choice in web browsers, unfairly favoring Internet Explorer over alternatives like Firefox and Chrome. Unfortunately for Microsoft, the situation is now on the Senate Judiciary Committee's radar, and they will look into claims that Microsoft is engaging in anti-competitive behavior. That said, it could be a difficult case to make, since Windows RT is destined for ARM-based tablets, and Apple currently dominates that market. 'When it comes to proving abuse of monopoly power, an important question is determining the market in which a monopolist has power — the relevant market, in antitrust legal terms. In the [late '90s] DOJ case, U.S. District Judge Thomas Penfield Jackson's findings of fact concluded Microsoft had a monopoly in the market for "Intel-compatible PC operating systems." Windows on ARM doesn't run on x86 chips, so by Jackson's standards, Windows RT hasn't been judged to be part of Microsoft's monopoly.' Microsoft addressed some of these issues in a blog post in February."

nk497 writes "Mozilla has accused Microsoft of trying to go back to the 'digital dark ages' by limiting rival browsers in the ARM version of Windows 8. Third-party browsers won't work in the desktop mode, and Metro style browsers will be limited in what APIs they can use, said Mozilla general counsel Harvey Anderson, forcing users to move to IE instead. Mozilla said it was the first step toward a new platform lock-in that 'restricts user choice, reduces competition and chills innovation,' and pointed out that such browser control was exactly what upset EU and U.S. regulators about IE in the first place. Anderson called on Microsoft to 'reject the temptation to pursue a closed path,' adding 'the world doesn't need another closed proprietary environment.'"

CWmike writes "Mozilla is working on a revamp of Firefox to synchronize its various versions — desktop, tablet, phone and Windows 8 Metro — into a single visual style, according to documents posted by members of its user interface (UI) design team. The project, which does not have a name, and the earlier blending of Mozilla's mobile and desktop design groups, is meant to bring more coherence to the various versions of the open-source browser. 'One of our major goals for the year [is] getting Firefox to feel more like one product — more 'Firefoxy' — across all our platforms, desktop to tablet to phone,' Madhava Enro of the Mozilla UI design team, said in a post to his personal blog on Tuesday. Enro posted a slideshow he and others used the week before to present their proposals at a company get-together. According to the presentation, some UI elements will be shared across all Firefox editions, among them a lean toward 'softer texture' and smoother curves in the design."

MrSeb writes "Firefox 12 has been officially released, with only one major new feature: A silent, background updater. Now you will have to approve the Firefox Software Updater when you first install Firefox, but after that the browser will update silently — just like Chrome. In other news, the Find feature now reliably centers the page on any matches — hooray!" Here are the release notes, the list of bug fixes, and the download page.

An anonymous reader writes "The Guardian newspaper has teamed up with Mozilla to research the monitoring of online behavior through cookies and other web trackers. After downloading the Collusion add-on for Firefox, you can generate a visual representation of all the cookies that have been downloaded which are linked to the sites you have visited. This shows quite an interesting picture. The Guardian staff then want the data from Collusion to be uploaded to their site, after which they say 'we can build up a picture of this unseen world. When we've found the biggest players, we'll start tracking them back — finding out what data are they monitoring, and why.'"

Trailrunner7 writes "Mozilla is developing a feature in Firefox that would require some user interaction in order for Flash ads, Java scripts and other content that uses plugins to play. In addition to easing system slowdowns, the opt-in for Web plugins is expected to reduce threats posed by exploiting security vulnerabilities in plugins, including zero-day attacks. 'Whether you hate them or love them, content accessed through plugins is still a sizable chunk of the web. So much so, that over 99% of internet users have Flash installed on their browser,' writes Mozilla's Jared Wein, the lead software engineer on the project, in a blog post."

Trailrunner7 writes with this excerpt from Threatpost: "Mozilla has made a change in Firefox that will block all of the older versions of Java that contain a critical vulnerability that's being actively exploited. The decision to add these vulnerable versions of Java to the browser's blocklist is designed to protect users who may not be aware of the flaw and attacks. 'This vulnerability — present in the older versions of the JDK and JRE — is actively being exploited, and is a potential risk to users. To mitigate this risk, we have added affected versions of the Java plugin for Windows (Version 6 Update 30 and below as well as Version 7 Update 2 and below) to Firefox's blocklist. A blocklist entry for the Java plugin on OS X may be added at a future date. Mozilla strongly encourages anyone who requires the JDK and JRE to update to the current version as soon as possible on all platforms,' Mozilla's Kev Needham said."

In order to provide an alternative to IE on Windows 8, Firefox needs a Metro UI. Luckily, development of a Metro interface for Firefox is well underway. The current build reuses the Android interface XUL (by virtue of being based on Fennec). The latest test release features lots of platform integration support: "We have Metro snap working, you can snap another Metro app to the right or left of Firefox and continue browsing. We also have HTML file input controls tied up to the Metro file picker. ... implemented the Windows 8 search contract, you can use the Search Charm from any screen on Windows 8. If you enter a URL, it will be loaded. If you enter anything else, it will be searched in your default search engine. We also implemented the Windows 8 share contract, you can use the Share Charm from any Firefox page to share that page to another application. Once you select the Share Charm it will list the applications you can share to, for example: Mail, Twitter, or Facebook." If you're interested in following development, the team has made a Mercurial repository available.

snydeq writes "Mozilla's 'endless parade' of Firefox updates adds no visible benefit to users but breaks common functions, as numerous add-ons, including the popular open source TinyMCE editor, continually suffer compatibility issues, thanks to Firefox's newly adopted auto-update cycle, writes InfoWorld's Galen Gruman. 'Firefox is a Web browser, and by its very nature the Web is a heterogeneous, uncontrolled collection of resources. Expecting every website that uses TinyMCE to update it whenever an incremental rev comes out is silly and unrealistic, and certainly not just because Mozilla decided compatibility in its parade of new Firefox releases was everyone else's problem. The Web must handle such variablility — especially the browsers used to access it.'"

suraj.sun writes with a followup to last week's news that Mozilla was thinking about reversing their stance on H.264 support. Mozilla chairman Mitchell Baker and CTO Brendan Eich have now both written blog posts explaining why they feel H.264 support is no longer optional. Eich wrote, "We will not require anyone to pay for Firefox. We will not burden our downstream source redistributors with royalty fees. We may have to continue to fall back on Flash on some desktop OSes. I’ll write more when I know more about desktop H.264, specifically on Windows XP. What I do know for certain is this: H.264 is absolutely required right now to compete on mobile. I do not believe that we can reject H.264 content in Firefox on Android or in B2G and survive the shift to mobile. Losing a battle is a bitter experience. I won’t sugar-coat this pill. But we must swallow it if we are to succeed in our mobile initiatives. Failure on mobile is too likely to consign Mozilla to decline and irrelevance." Baker added, "Our first approach at bringing open codecs to the Web has ended up at an impasse on mobile, but we’re not done yet. ... We'll find a way around this impasse."

An anonymous reader writes "Adoption of the HTML5 video element has been hampered by the lack of a universal video format that is supported in all browsers. Mozilla previously rejected the popular H.264 video codec because it is patent-encumbered and would require implementors to pay royalty fees. The organization is now rethinking its position and is preparing to add support for H.264 video decoding in mobile Firefox via codecs that are provided by the underlying operating system or hardware. The controversial proposal has attracted a lot of criticism from Firefox contributors, including some employed by Mozilla."

An anonymous reader writes "News from the world of AmigaOS that the Beta version of Timberwolf (a.k.a. Firefox) was made available last month." Timberwolf is a port of Firefox to the AmigaOS (the name change is for similar reasons to Debian's use of Iceweasel name) and has been under development for quite some time. The AmigaBounty project page has screenshots and even more info for those interested. There's a video of the browser in action, but beware of the cheesy soundtrack.

Mooga writes "I am a hard-core user of Firefox 3.6.x who has chosen to stick with the older, yet supported version of Firefox for many years now. However, 3.6.x will soon hit end-of-life, making my life, and the lives of similar users, much more complicated. 3.6.x has been known for generally being more stable and using less RAM than the modern Firefox 10 and even Chrome. The older version of Firefox is already having issues rendering modern websites. What are others who have been holding onto 3.6.x planning on doing?"

New submitter dr_blurb writes "After reading about last year's hoax report 'Intelligence Quotient (IQ) and Browser Usage' I realized I was in fact already running a real live experiment measuring number skills: a site were you can solve Calcudoku number puzzles. I analyzed two years' worth of data, consisting of over 1 million solved puzzles. This included puzzles solved 'against the clock,' of three different sizes. For each size, Chrome users were the fastest solvers, Firefox users came second, and IE users were the slowest. The number of abandoned puzzles (started but never finished) was also significantly higher for IE users. Analysis shows that the differences are statistically significant: in other words, they did not happen by chance. I put up more details and some graphs, and also wrote a paper about it (PDF)."

An anonymous reader writes "While there is now the possibility of using 3D in the browser over WebGL, it is still hard for regular web developers to get 3D content into websites without being hardcore graphics programmers. XML3D, a project at the Intel Visual Computing Institute, tries to tackle that problem by having a very easy-to-use language as an extension of HTML5. The goal is to standardize it with the W3C. There are already modified Firefox and Chrome browsers that support XML3D natively. At Intel's Research Blog you can find a video on what shopping at an online store could soon look like. In the example, the user purchases a DSLR that can be fully interacted with in 3D, including attaching various lenses and an external flash."