In this issue…
Firefox 3.1 beta 1 now available
Firefox 3.1 beta 1 is now available for download. This milestone is focused on testing the core functionality provided by many new features and changes to the platform that are scheduled for Firefox 3.1. Ongoing planning for this release can be followed at the Planning Center, as well as in the mozilla.dev.planning discussion group, and on IRC in the #shiretoko channel.
New features and changes in this release include: web standards improvements, added support for CSS 2.1 and CSS 3, a new tab-switching shortcut that shows previews of the tab you’re switching to, improved control over the Smart Location Bar, support for the new video and audio elements, the addition of the W3C Geolocation API, JavaScript query selectors, web worker threads, SVG transforms, and improved support for offline applications.
More information about these features are available in several places including the Mozilla Developer Center’s Firefox 3.1 for Developers article, and in the Web Tech blog’s Overview of features for Web Developers post.
Thunderbird “Shredder” alpha 3 released
The third early release of Thunderbird (code-named Shredder) is now available. This release is called “alpha 3″ to emphasize its early nature and that it is not suited to regular, daily use. The alpha is available for testers, extension developers, and other people who are curious to follow the development of the next release of Thunderbird. Shredder Alpha 3 includes initial versions of some new features, and you can find more details on the release page and notes.
First Mobile Firefox alpha released
Mobile Firefox (code-named Fennec) has reached its Milestone 9 release, which is also its first alpha. The team is calling this the “User Experience alpha”, and it is targeted at the Nokia N800/N810 internet tablet. While great progress has been made on the Windows Mobile version, it is not ready for general use and is thus not included in this release. There are, however, new desktop versions of Fennec available, meaning you can now install the mobile browser on your Windows, OS X, or Linux desktop to see what all the fuss is about (and to help with testing and feedback, of course).
The Fennec Alpha 1 release notes include information about how to get started, how to install the browser, what’s new in this release, a list of known issues, and how to provide feedback. If you’ve ever been interested in getting involved with the Firefox Mobile project, now is a great time to install Fennec, watch the walkthrough video, and get started.
Impact Mozilla: last call for submissions
The Impact Mozilla community marketing challenge comes to a close on Friday October 24th, so this is your last opportunity to submit a one or two page idea summary. The purpose of this challenge is to help improve Firefox user retention. We know that tens of millions of people have downloaded Firefox but don’t continue to use it today. How do we get these past users back? How to we keep future users active once they’ve downloaded Firefox? If you have an idea about how we could solve this problem, we urge you to write it up and submit it through the Impact Mozilla website on or before this coming Friday.
Localization schedule for Firefox 3.1 beta 2
Seth Bindernagel has posted the localization schedule for Firefox 3.1 beta 2. The string freeze is going to be on Thursday, October 30 at 11:59pm (Mountain View time), which is just over a week from now. Code freeze will be Tuesday, November 4 at 11:59pm (Mountain View time). If you did not make Firefox 3.1 beta 1, we would love for you to participate in this next beta release. We have a goal of releasing a fully localized beta, so please let us know what we can do to help you get into the second beta. For more information and links to the localization team tools, please see Seth’s weblog post.
Discussing Mozilla’s proposed 2010 goals
Last month, Mitchell Baker posted a list of proposed goals she believes Mozilla should work towards achieving by 2010. Now Mitchell is looking to expand and continue the discussion around these proposed goals, and she has written a blog post outlining the next steps we’ll be taking towards ensuring that the whole Mozilla community has an opportunity to participate in the discussion and provide thoughts and feedback. “Mozilla has many groups of people who work together on particular aspects of Mozilla products, technology, adoption and mission. These groups are a natural setting for discussing the overall goals of the Mozilla project, and what motivates people to contribute. With that in mind, we’re planning a set of discussions to give more people a chance to participate comfortably. Some of these will be face-to-face meetings; others will be online discussions.” For more information about these smaller group discussions and other forums that are available for ongoing feedback, see Mitchell’s blog post.
Developer tools and the Open Web
Mozilla Labs recently announced the formation of a new group that will focus on the research and development of developer tools for the Open Web. “We believe that there’s tremendous opportunity for innovation in tools that increase developer productivity, enable compelling user experiences, and promote the use of open standards.” Dion Almaer and Ben Galbraith, co-founders of Ajaxian, the Ajax Experience, and long-time supporters of the Open Web have joined Mozilla in a full-time capacity to lead the new project. For more information, please see the Mozilla Labs blog post.
Ubiquity: turning bookmarklets into commands
Aza Raskin has put together a short video tutorial on how to turn your Firefox bookmarklets into Ubiquity commands. “Bookmarklets are clickable actions (technically a link containing some Javascript) that can be added to the bookmarks bar of your browser. They’re a good way of getting control of the web back into users’ hands, by allowing them to add whatever new functionality they want to the websites they visit. The main problem with bookmarklets is that they don’t provide a scalable solution for accessing their functionality. You can only have so many buttons on the toolbar before they become unusable.” There’s a new utility function in Ubiquity that makes it trivial to turn any bookmarklet into a Ubiquity command, and Aza’s video tutorial shows you how to do it.
Add-on developers: it’s that time again
Justin Scott writes, “With the release of the first beta of Firefox 3.1 comes everyone’s favorite release-time festivity: extension compatibility updates! If you’re an extension developer using a maxVersion of 3.0.* or less, please test your extension before declaring 3.1b1 compatibility. Some of the changes for extension developers are listed [at the Mozilla Developer Center]. 3.1.b1 is an allowed version on AMO, but 3.1.* will not be added until closer to final release. Keep in mind that you can always look at the Developer Statistics Dashboard to see how many of your users are on 3.1 betas and may be marked as incompatible/disabled.” For more information you should check out Justin’s blog post.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
Please note: Firefox 3.1 Beta 1 is a public preview release intended for developer testing and community feedback. It includes many new features as well as improvements to performance, web compatibility, and speed. We recommend that you read the release notes and known issues before installing this beta.
Firefox 3.1 Beta 1 is now available for download. This milestone is focused on testing the core functionality provided by many new features and changes to the platform scheduled for Firefox 3.1. Ongoing planning for Firefox 3.1 can be followed at the Firefox 3.1 Planning Center, as well as in mozilla.dev.planning and on irc.mozilla.org in #shiretoko.
New features and changes in this milestone that require feedback include:
More information about new web developer features are available in the Web Tech blog post.
Testers can download Firefox 3.1 Beta 1 builds for Windows, Mac OS X, and Linux in 36 different languages. Developers should also read the Firefox 3.1 for Developers article on the Mozilla Developer Center.
Note: Please do not link directly to the download site. Instead we strongly encourage you to link to this Firefox 3.1 Beta 1 milestone announcement so that everyone will know what this milestone is, what they should expect, and who should be downloading to participate in testing at this stage of development.
In this issue…
Mozilla Labs in Europe next week
Aza Raskin writes, “Mozilla Labs will be making its way to Europe next week to meet with community members, hackers, bloggers, media types, and general feasance doers. We’ll be spending time in London, Berlin, and Barcelona. We’ll be having Labs nights, Hack sessions, or drinks in each of the cities. They are open to everyone, so we hope you can join us!” More details, including a rough schedule of events, are available at Aza’s weblog.
Introducing Geode
Geode is a new add-on that allows developers to begin experimenting with geolocation technologies and concepts in Firefox 3. Future versions of Firefox plan on supporting the new W3C Geolocation Specification, which adds the native ability for Web sites to request, and for you to optionally grant access to, your location. These should be available for users to play with in upcoming beta releases of Firefox 3.1, as well as alpha releases of Mobile Firefox (Fennec). Geode provides an early implementation of this new technology so developers can work on and test concepts that include location-aware experiences using Firefox 3 today. The add-on includes a single experimental geolocation service provider so that any computer with WiFi can get accurate positioning data. The initial Mozilla Labs blog post includes lots of information about how Geode works, where to download it, some ideas of how it could be used, and how to participate in discussing ideas and possible experiments. Aza Raskin has also written a follow up post about Geode that delves into some of the questions that have emerged about the add-on since its initial release.
New Mozilla public relations weblog
Mozilla’s PR team has unveiled a brand new weblog called “Above the Fold: Mozilla in the News”. “Above the Fold is a place where the community can come to gain insight into public relations at Mozilla. We will keep track of news cycles around announcements, competitor news and general industry trends. We’ll then provide context around why particular articles and dialogues are important to Mozilla.” If you’ve ever been interested in public relations, how it works and what it all means, you should keep an eye on Above the Fold.
SUMO: Article editor ideas wanted
The team over at support.mozilla.com (SUMO) is looking for ideas about how to improve the SUMO Knowledge Base editor system. Discussion and feedback is happening over on the SUMO Contributors forum, and there is still time for you to post your thoughts and ideas about the problems you have with the current editor and possible ways to fix those issues. A list of some of the problems and solutions that have already been posted is available over on the SUMO blog.
Firefox accessibility team needs your help
Marco Zehe writes, “If you’re not afraid to get your hands dirty a bit and would like to help the Firefox accessibility team, now would be a good time to get involved. The code that calculates the names for any created accessibles has been growing over time and became largely unmaintainable. New features such as adding the aria-label property support requires code duplication for HTML and XUL, and in general the code has many stylish un-niceties. Our team has started a code cleanup and code refactoring series to get the code into better shape.” As with any refactor, there is a risk of regressions that cannot be discounted. The team is looking for help in testing for these possible regressions and for help filling in any gaps that exist in the suite of available testcases. This is a really great way to get involved with Mozilla development efforts, so if you’re interested in helping out you should read Marco’s blog post to get started.
SVG external document references
In a post over at the Web Tech weblog, it has been announced that SVG external document references have landed on trunk in time for the second beta of Gecko 1.9.1 and Firefox 3.1. “What this means is that the SVG element being used as fill, clip path, mask, filter, svg:use target, or marker no longer needs to be in the same document as the element being filled, masked, filtered, etc. In particular, what this means is that the preceding post about SVG effects in HTML content now applies to HTML documents, not just XHTML.” For further details and a link to a small demo, see the Web Tech blog post. Robert O’Callahan has also written about recent SVG development on his weblog.
Audio, Video, Geolocation, and Media queries documentation
Eric Shepherd has been hard at work documenting some of the exciting new web technologies that are slated for inclusion in Firefox 3.1. The first of these is the HTML 5 audio element that is used to embed sound content in an HTML or XHTML document. Similarly, the HTML 5 video element documentation is available, explaining how to use this element to embed video content. Eric has also put together a “Using geolocation” article that introduces the new geolocation API that is being developed for Firefox 3.1. Finally, the documentation for CSS media queries — allowing different style sheets to be selected based on very precise criteria — has been finished.
Help wanted: QA Companion Firefox add-on
Clint Talbert writes, “Zach Lipton and Ben Hsieh created the QA Companion Add-on. This is an extension that sits in a little window outside Firefox or Thunderbird and helps you run litmus tests against the application. It has helped hundreds of people when testing Firefox, and has become a central part of our QA Test Day events. The QA Companion has great potential, lots of poeple have thought about ways to do more interesting mash-ups with it, including integrating some of the Nightly Tester Tool functionality, integrating Mozilla automation UI, etc. If you’ve always wanted to work on an Add-on but it seemed like too big of an undertaking, this is a great opportunity. The base code is already written, and it’s all pretty straightforward. Together, we can design a new direction for the tool and make it a really useful item for all the testers out there in Mozilla Land.” If you’re interested in helping the QA team out with the development and maintenance of the Companion, Clint asks that you leave a comment over on his blog post.
Ubiquity progress
A release candidate for Ubiquity 0.1.2 has been made available, and the team is asking for help with testing. 0.1.2 contains a preliminary version of the parser-localization API that Jonathan DiCarlo discussed in an earlier blog post, and that he has described in detail in his parser localization API tutorial. Complete release notes are available for 0.1.2, and further information about and download links for the release candidate are available at Jonathan’s weblog.
SUMO: Live Chat and community participation
Matthew Middleton, the new leader of the SUMO Live Chat project, has written an interesting article about the Live Chat facility and its contributor community. “One great thing about support as a community is that the line between user and helper is blurred. Many of the current support volunteers got started by asking a question themselves, staying around to help other people using information learned solving their own problems. While most users don’t have time to commit regularly, many users have spent extra time to troubleshoot an issue, to let us know what finally fixed a problem, or to post advice in the forum. The support community allows new helpers to learn about Mozilla and support in general, while actively helping users solve problems.” As always, the SUMO team could use more help, and if you think Live Chat might be right for you, you should read Matthew’s post to find out how to get started.
MozAfterPaint: new experimental API
As posted on the Web Tech blog, the Firefox 3.1 team has created a very experimental API for Firefox 3.1 that fires an event every time content is repainted. “The event is called MozAfterPaint and is fired at the document, bubbling up to the window. The event offers two attributes, clientRects and boundingClientRect, which tell you what was repainted, using the same objects and coordinate system as the getClientRects and getBoundingClientRect methods. This is very useful for Firefox extensions and other ‘chrome’ code that might be using the canvas.drawWindow method to capture the contents of windows. It might also be useful for tools like Firebug. But it’s also potentially useful for regular content, for example if you want to add some lightweight JS instrumentation to a page to measure what gets painted by Firefox, and when.” For more information about this new API, read the post over on Web Tech.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
In this issue…
Impact Mozilla: Community marketing challenge
Last week Mozilla’s marketing team launched a new community-focused marketing challenge called Impact Mozilla. The idea is to further open Mozilla’s marketing process to the community, and to see who can come up with the best ideas. This challenge is specifically focused on gathering and developing ideas that will help increase Firefox’s user retention rate — increasing the number of people who continue using Firefox after downloading and installing it.
“We’re looking for innovative ways to make sure people who download Firefox become regular users. Interested? Start by sending us a summary of your ideas and an oveview of how you and your team will carry them out. If your initial strategy makes the cut, we’ll ask for a complete plan detailing your solution. If your plan is selected as the winner, you’ll have the opportunity to manage a marketing campaign for one of the top brands in the technology world. We’ll give you the resources to enact your solution, plus $3,000 for the winning proposal.” For all the details, including how to get started and where to submit your plans, see the Impact Mozilla website.
Free Software and Open Source Symposium (FSOSS)
David Humphrey writes, “The Free Software and Open Source Symposium (FSOSS) is scheduled for Oct 23 and Oct 24, and online registration is open. There are various early bird rates, so register early. This year’s line-up includes many familiar Mozilla faces. The list of speakers is long and diverse, and represents the best of the web, the open source desktop, open source business, policy, law, etc. We’re also going to be running a track on Teaching Open Source, which will bring together professors, students, administrators, and community leaders to discuss the potential and challenges of taking students into open source projects.” For more information, check out David’s full blog post, and check out the FSOSS web site.
Mobile Firefox: User Experience developments
Mobile Firefox (code-named “Fennec”) recently hit its milestone 8 (M8) release. Mark Finkle blogged about the release at the time, and Madhava Enros has since blogged about the user-experience changes and additions to the mobile browser. “This is an exciting time from a user-experience perspective because, along with functionality and stability improvements, this milestone brings with it the beginnings of Fennec’s look and feel. In a sense, we have some UI worth playing with, evaluating, and improving.” Madhava’s post includes a bevy of screenshots that you can check out, and if you would like to take part in the discussion about the Mobile Firefox UI, you should do so over in the Mobile development group.
Spread Firefox Affiliates program
David Rolnitzky recently announced a number of improvements to the Spread Firefox Affiliates program. The Affiliates program is designed to make it easier for our community to spread the word about Firefox by providing website buttons and banners, as well as quarterly prizes for the top Firefox referrers. “Some of the improvements are user-facing and some of them are back-end improvements which, while not immediately obvious, will be of great benefit to the program. You can find the initial details for this improvement plan here.” Improvements include clearer information about how to get started and how the points system works, better organization of buttons and banners, a new selection of international buttons, the ability to create custom buttons, and a new incentive system. Read David’s blog post for full details, and then head over to the Affiliates program site to sign up and learn how you can help make Firefox even better.
Next steps for SpreadFirefox.com
A number of improvements have been made to SpreadFirefox.com (SFX) over the summer, and Alix Franquet has been closely involved with that work. Alix has now blogged about the next steps for SFX, outlining a three-part redesign that will be undertaken towards improving the homepage and overall site navigation. These three parts include: creating a simplified homepage that better explains what SFX is about and that includes a community spotlight and a call to action; a new page for SFX members to track activity so they can better see what’s happening on the site including events, new groups, and new posts; and updating the site navigation to improve overall usability. There are lots more details about the planned changes in Alix’s blog post, and you can read the full plan over on SFX itself. We’re always looking for more help with SFX, so this could be a great opportunity to dive in and get involved with Mozilla’s community marketing projects.
Mozilla Public Relations metrics
Mozilla’s Public Relations team has been working on opening up the PR process, making it more transparent and more in fitting with Mozilla’s open source DNA. Their most recent foray is a post written by Melissa Shapiro, in which she discusses PR metrics. “How do we know if we’re getting better if there’s no baseline indication of impact? The answer isn’t a pure science. True PR metrics are not just quantitative but qualitative as well. Quantitative analysis explores things like total number of articles, mentions in the press, coverage by country, etc. Qualitative analysis includes message penetration as well as audience and tone analysis. It turns out they are equally important in evaluating the success of Mozilla’s major PR initiatives.”
The article goes on to discuss the various types of quantitative and qualitative analysis we explore as part of our PR process at Mozilla, outlining use cases for each and giving examples comparing the public relations activities around the Firefox 2 and Firefox 3 releases. If you’re interested in learning more about the normally opaque world of public relations, you should check out Melissa’s blog for this and other articles.
The vision for SUMO - Part 8: Live Chat
David Tenser has published an extensive series of blog posts where he has been discussing a comprehensive vision for the scope and role of the Support.mozilla.com (SUMO) project. He has recently published the eighth post in the series, this one focused on the innovative and incredibly useful “Live Chat” feature. “If a problem isn’t yet covered in the Knowledge Base, or if the instructions in the article are too hard to understand, Live Chat is a powerful way for users to get in touch with Firefox experts and get hands-on assistance in solving their problems. Live Chat can also be a very fun way for contributors to provide support. Contributors helping out with Live Chat don’t just help users, they talk to each other in the backchannel as well, providing assistance to other helpers whenever needed. This means that although you’re usually the only one interacting with the user you’re helping, you’re never alone.”
David further discusses some possible future improvements for the service, including a fully integrated chat client, a simple scheduling solution, support for languages other than English, and automatically saving chat logs and associated user happiness ratings, among other things. If you’re interested in the Live Chat feature of the SUMO project and would like to see how the team is thinking about improving it in the future, read the full post over at the Firefox Support Blog.
Add-on developers survey: raw results
The team responsible for the Addons.mozilla.org (AMO) site recently conducted a survey of the add-on developer community. A total of 265 people responded to the survey, and the initial results have been published. “The general summary is that most respondents were individual developers with 2 or more years of add-on development experience. Naturally they felt comfortable with JavaScript and XUL. They primarily built add-ons for Firefox and hosted them on their own.” The full results have been published, but they are simply the raw results. The team will be applying some correlation analysis to draw out more interesting findings and conclusions. To view and discuss these initial results, see the post on Basil’s weblog.
Two Mozillians make BusinessWeek’s “25 Most Influential”
It was recently announced that Mitchell Baker and Joi Ito were both included on BusinessWeek’s list of the 25 most influential people on the Web. “Each year, we turn to readers and BusinessWeek staff for the Best of the Web list, asking them to contribute names for a list of the Internet’s movers and shakers.” Watch the full slideshow, which includes all 25 honorees, over at BusinessWeek.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
In this issue…
Fennec M8
Mark Finkle has written about Fennec M8 being released. M8 is the latest
pre-alpha milestone release of the Fennec mobile browser which will
eventually become Firefox Mobile. M8 includes a new set of icons that Sean
Martell and Madhava Enros wrote about, improved rendering performance, UI
improvements and a pile of other items. You can find a full summary in
Mark’s post.
Camera Input Tag
As discussed on a post on Ajaxian, Brad Lassey has put up a screenshot of
Fennec taking input from a camera and making it available to web
applications. This kind of functionality would work much like a file input
tag that uploads pictures instead of files off your hard drive. This means
that web sites could easily include support for uploading pictures directly
from the browser instead of having to go through a cumbersome gallery and
file upload procedure. Read Brad’s post for full details.
TraceMonkey for Fennec
Vladimir Vukićević has posted about the work that he did to bring
TraceMonkey to the ARM platform. TraceMonkey is Mozilla’s fast JavaScript
implementation that will be included in Firefox 3.1. The speedup on ARM is
similar to what was measured on x86-based systems. Some operations are 30x
faster with a roughly 2x speedup on the whole of the SunSpider test. These
speedups will offer many user-perceptable improvements for web sites. But
because much of Fennec is written in JavaScript, it will also improve the
performance of the browser as a whole. Read Vlad’s post for more
information.
Add-ons for Mobile
Extensions are one of the best parts of Firefox on the desktop and Mozilla
has been working hard to bring that same extension experience to Fennec.
Early initial support for extensions was included in Fennec M7 and has been
improved in M8. Mark Finkle has a post up about what’s going to be required
by extensions authors and a couple of sample add-ons that people can build
off of.
In this issue…
Mobile Firefox: milestone 8 released
Mark Finkle posts that Fennec (the code-name for Mobile Firefox) has reached a milestone 8 (M8) release, which you can install and test on a Nokia N8×0. “One of the big improvements during this milestone was the addition of several Mozilla QA team members. Fennec is being tested pretty hard now, and by people who love to find bugs. We are finding and fixing lots of issues now. Probably the biggest visible change in M8 is the new theme. It’s not entirely landed yet and will likely get some tweaks as we iterate on the design.” The post goes on to talk about some upcoming changes for Fennec. “Although Fennec is still only targeted for the Nokia N8×0, that should be changing fairly soon. Work on Windows Mobile has heated up quite a bit.” For more information, including a list of M8 highlights, see Mark’s full article.
Weave: the story so far
Dan Mills has written an extensive update about the status of the Mozilla Labs “Weave” project, outlining the project’s background, its current state, and setting up some questions about its potential future. “We think Weave still has a long way to go, and the real questions are: What do we need to do to get closer to our vision? What are the main problem areas right now? And, do we need to revisit any old decisions? Now that we’ve been running this experiment for a while, I think we can begin answering those questions.” Dan’s post goes on to discuss some of the major issues facing the project, which he’ll continue to expand upon in an upcoming post. You can read the full text of his current post over on his weblog.
Usage data: some basic examples
Mitchell Baker has written before that she believes there is a need to make basic, aggregate, anonymized information about Internet usage more widely available. “If everything that is known about the basic usage of the Internet is closed and proprietary then the Internet as an open platform will suffer.” Mitchell has now posted some examples of what she means by “usage data”, most of which we’re quite accustomed to seeing in aggregated, anonymized forms. These include a site’s bandwidth usage, site “traffic” in a day or month, and software download numbers. “These examples are clearly very general. I use them precisely for this reason — to demonstrate that we already understand the usefulness of this type of data and that it can be presented in an aggregate, anonymous form. There are other forms of aggregate, anonymous data that can be equally useful in understanding how the Internet is being used and ultimately, understanding what the Internet really is.” To read Mitchell’s full post, visit her weblog.
Help design the new SUMO logo
The support.mozilla.com (a.k.a. SUMO) project has been underway for over a year now, and has become an amazing community-powered support channel impacting millions of Firefox users around the world. The SUMO team has been working on envisioning the future of SUMO, conceptualizing the service’s evolution as it grows both in scope and participation. As part of this evolution, Tara Shahain and David Tenser hope to develop a strong visual identity for the project that encompasses SUMO and its ongoing mission. Part of this involves creating a new logo for the project, but they need your help. “More specifically, we need your help in brainstorming ideas around the design concept and how best to represent SUMO visually. In the past SUMO has dedicated its resources to Firefox and is therefore primarily known as ‘Firefox Support’. But as David notes in his blog, SUMO aspires to be much more.” To learn more about the project and how to participate in the logo design process, see Tara’s weblog post.
New Firefox logo style guide
John Slater and Tara Shahain have been working on developing a new and improved style guide for the Firefox logo, with the aim of refining existing guidelines and communicating those out to the widest possible audience. Last Friday, John announced that the new style guide has been released. “Our hope is that this guide will answer many of the commonly asked questions about how (and how not) to use the logo. We’ve also included a section where people can download the various configurations so there won’t be any confusion about what the official versions are. [W]e’re calling this style guide a beta launch for now because we want to make sure the community at large has a chance to review and weigh in before we officially declare it final. So, if you have any questions, thoughts or comments please let me or Tara know, or post your feedback on the Spread Firefox discussion page.” For full details, see the complete post on John’s weblog.
Powered by Mozilla FAQ
David Boswell has been working on creating some guidelines to determine how the “Powered by Mozilla” logo can be used as part of projects and products. He has recently posted a Powered by Mozilla FAQ that answers the questions he’s seen asked during the ongoing conversation about the logo. “Some more information (guidelines about the logo and an application to request using the logo) still need to be posted and those pieces will be coming soon. For now though, I’m posting the FAQ to let people give us some more feedback before the other pieces are finished up.” More information about the FAQ and the Powered by Mozilla project is available through David’s weblog post.
Mozilla Community Store: opening soon!
Part of the Firefox 3 launch included a t-shirt contest in which we “open sourced” the design process to create the official Firefox 3 t-shirt. Not only did we get a fantastic winning shirt, we also received a huge number of other great designs. There’s been a growing demand to make more of these community designs available for purchase, so for the past few months the Marketing team has been sorting out the legal and logistical challenges to make this possible. Tara Shahain has recently announced the good news that “we’ve partnered with Zazzle.com to create the ‘Mozilla Community Store’ — a sidekick to the original Mozilla Store which will serve as a new and open channel for community generated products. The Community Store isn’t quite finished yet, but I hope to have it ready in the next month or so. Make sure to start thinking of your designs! Once it launches, we’ll have plenty of details to help guide you through the entire process. Stay tuned!” More information about this project is available on Tara’s weblog.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
In order to repair a problem experienced by some users with the Password Manager feature in Firefox 3.0.2, and as part of Mozilla Corporation’s ongoing stability and security update process, Firefox 3.0.3 is now available for Windows, Mac, and Linux as free downloads at http://getfirefox.com/
We strongly recommend that all Firefox users upgrade to this latest release. If you already have Firefox 3 or Firefox 2, you will receive an automated update notification within 24 to 48 hours. This update can also be applied manually by selecting “Check for Updates…” from the Help menu.
For a list of changes and more information, please review the Firefox 3.0.3 Release Notes.
As part of Mozilla Corporation’s ongoing stability and security update process, Firefox 3.0.2 and Firefox 2.0.0.17 are now available for Windows, Mac, and Linux as free downloads:
We strongly recommend that all Firefox users upgrade to this latest release. If you already have Firefox 3 or Firefox 2, you will receive an automated update notification within 24 to 48 hours. This update can also be applied manually by selecting “Check for Updates…” from the Help menu.
For a list of changes and more information, please review the Firefox 3.0.2 Release Notes and the Firefox 2.0.0.17 Release Notes.
Note: All Firefox 2.0.0.x users are encouraged to upgrade to Firefox 3.0.2 by downloading it from http://getfirefox.com/.
In this issue…
Labs Meetup this Thursday in Mountain View
Mozilla Labs is holding its monthly meetup this Thursday, Sept 25, at Mozilla HQ in Mountain View (1981 Landings Drive, Bldg K). This month the conversation will focus on the future of the Web — “We want to hear from you! What is your big idea for the future of the Web? Do you have thoughts to add to the Concept Series? We are anxious to hear what inspires you!” Everyone is welcome to drop by and participate in the meetup, so if you’re in the Bay Area you should take the time to stop by and join the conversation. If you’re planning to attend, please RSVP in the comments over at the Mozilla Labs Meetup post.
AMO developer tools ready for testing
Justin Scott has been writing about the development of new tools for addons.mozilla.org, and has now announced that those tools are ready for testing. “On the en-US Developer Tools index, you should now see an invitation to try out the new tools, which will take you to the new ‘Developer Dashboard’. Using the old index will continue using the old tools until the next update when we intend to make the tools the default and only tools.” There’s also a test site available, where you can play around with the new tools without causing changes on the live AMO database. For details about the various new tools, you should read Justin’s previous posts, all of which are linked in his blog post.
SVG effects for HTML content
Robert O’Callahan has been working on adding features to Firefox that allow SVG effects to be applied to HTML content. He originally posted about this work back in June, discussing his experiments with making SVG’s “clip-path”, “mask”, and “filter” properties work when applied to HTML content. Last week Robert announced that this work has been added to the main Mozilla code base, and further that he has submitted his proposal to the SVG working group for standardization. For more information about these new features, including screenshots of them in action and working demos, see Robert’s post on the Web Tech weblog.
CSS transforms
The folks over at the Web Tech weblog have posted that Gecko (Mozilla’s layout engine) nightly builds now support a new “-moz-transform” CSS property. This property — a version of which is similarly supported by WebKit — is described as a “CSS property that accepts a list of transform functions (generic affine linear transforms) and then applies those transforms, in order, to the HTML elements the property is applied to.” Several examples of how to use the property and descriptions of what it does are available in the Web Tech post. “It will be interesting to see what uses developers find for CSS transforms. Much of the functionality once reserved for plugins can now be directly integrated into CSS and JavaScript.” More information and code samples are available in the Web Tech article.
Color profile support changes
Bobby Holley has been refining Mozilla’s color management backend, working to improve performance and polish the feature so it’s ready for “prime time”. These efforts have clearly paid off, as color profile support has now been turned on by default for tagged images in the latest Firefox nightly builds. In this context, “tagged images” are any images displayed in the web browser that have an embedded ICC color profile — in other words, images that contain the information needed to do a specific and accurate color transformation. Bobby’s post goes into all the technical aspects of these changes in detail, and also discusses why color management hasn’t been enabled for everything at this time. Percy Cabello has also posted about these changes over at Mozilla Links.
nsITraceableChannel, intercept HTTP traffic
Jan Odvarko writes, “Since bug 430155 (’new nsHttpChannel interface to allow examination of HTTP data before it is passed to the channel’s creator’) is now fixed, it’s possible to intercept HTTP traffic from within a Firefox extension!” Jan estimates that this fix will be part of Firefox 3.0.3, and points out that this feature is crucial for Firebug as one of that add-on’s features is the ability to display the response of any HTTP request made by a page. To this point, Firebug has been making use of the Firefox cache and XHR monitoring to implement this feature, but there are several issues with this approach that make it suboptimal. For more information about this new feature, including examples of how to make use of it in Firefox add-ons, read Jan’s article at his Software is hard weblog.
Localization Drivers visibility
Seth Bindernagel, Mozilla’s Director of Localization, recently blogged about some steps the Localization Drivers team is taking to increase the visibility of localization activities and improve project communications. The two primary tools they’re using are the Localization Dashboard and the team’s new weekly triage meetings where they ensure that high priority issues are dealt with quickly. Additionally, the team has created a new Firefox 3 l10n release trackers bug, and are working to make it easier for new localization teams to navigate through the early stages of our process. The results of some of these efforts are clear, as Seth announces that there are likely to be 13 more languages added to Firefox in the 3.0.2 and 3.0.3 releases, which is a huge accomplishment in the span of two minor updates. For more about Mozilla’s localization work, see Seth’s full blog post.
New Mozilla Foundation t-shirt
David Boswell writes, “I’d like to let people know that there is a new Mozilla shirt available in the Mozilla store. This new design is heavily influenced by the old school Hack shirts.” As with all Mozilla Store purchases, proceeds directly benefit the Mozilla Foundation. You can check out (and order!) the t-shirts at the Mozilla Store.
Mozdev turns eight
The Mozdev team writes, “In September 2000 mozdev.org was launched as a site dedicated to supporting Mozilla application and extension developers. Over the last year we have continued to provide hosting for hundreds of active projects and there are now add-ons for over a dozen Mozilla-based applications. There are also new features and more updates coming that will make developing projects even easier. We would like to thank everyone who has contributed time, energy or money over the past 8 years and we look forward to another year of serving the Mozilla community.”
Latest about:addons newsletter
The Mozilla Add-ons team has published the latest issue of the monthly about:addons newsletter, bringing you the latest and greatest news and information from the world of Mozilla Add-on development. You can read the full newsletter at the Mozilla Developer Center and sign up to have future issues sent directly to your mailbox using the handy subscription form.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
In this issue…
Mozilla: Defining our 2010 goals
Mitchell Baker is leading the effort towards defining the 2010 goals for Mozilla and has recently posted a draft version of the proposed goals. Setting these sorts of wide-reaching aspirational goals is critical because “[a]rticulating a broad, commonly shared set of aspirations helps many disparate groups of people organize themselves and work towards very practical, concrete tasks that make our aspirations real.” The 2010 goals “should be concrete enough that people can respond to them and provide a means for evaluating the scope of progress. Perhaps even more importantly, these goals should express important ideas rather than specifying implementation plans.”
Mitchell’s initial post outlines the background and purpose of the goal setting process, and her second post includes the draft set of proposed 2010 goals that have emerged from various discussions including feedback gathered during the Firefox Summit. If you’re interested in the longer-term goal setting and direction of the Mozilla project, Mitchell asks that you “[p]lease take some time and review the proposed goals, make suggestions, ask questions, and make alternative proposals.” You are invited and encouraged to take part in this conversation, as these goals form the foundation of what it is that Mozilla does and aspires to become. Everyone is welcome to participate.
To take part in this conversation you should watch Mitchell’s weblog, as well as the mozilla.governance newsgroup, where further discussion topics will be posted. There’s also a new “#2010goals” channel in IRC (irc.mozilla.org) where you are welcome to engage in real time discussion regarding these goals.
Firefox add-ons developer survey
The addons.mozilla.org (AMO) team is looking for help as they work on improving the add-on development experience. “If you’ve developed or tried to develop an add-on for Firefox (or other applications), we’d like your feedback to know what we can do to improve that experience through documentation, tools, and features. Please take a few minutes to complete our survey. Your responses will be anonymous, and every response will be read. We’ll summarize the findings in a few weeks.” Add-ons are a vital part of the Firefox ecosystem, so any help you can provide here would be hugely beneficial to the project as a whole — Add-ons Developer Survey.
TraceMonkey and Firefox Mobile
Over the past few weeks, Vladimir Vukicevic has been working on getting TraceMonkey working on the ARM architecture which is frequently used in mobile and handheld devices. “[M]obile and handheld platforms are going to quickly become consumers of the full web, and core performance gains will often yeild much more significant user-perceptible performance improvements. The result of all this work will be a richer web experience on mobile and embedded devices, by allowing those users to take advantage of modern web applications that do much of their work on the browser instead of server side.” Vlad’s TraceMonkey work will be available for testing in the next alpha release of Fennec (the code name for Firefox Mobile) by enabling a configuration setting the same way testers can enable TraceMonkey in Firefox nightly builds. For more information, including a host of technical details, see Vlad’s weblog.
Firefox support: Envisioning the future
David Tenser, Mozilla’s SUMO project lead, has been writing a multi-part weblog post outlining a working vision for the future of the Firefox support project. “Since the SUMO team was formally created, we have grown from a fairly buggy web site managed by a tight group of people, to a truly community-powered support channel with over 70 active contributors per week. This is an amazing achievement that really shows the strength of the Mozilla community.” Even so, SUMO’s mission is not complete. David continues, “From my perspective, we’ve just started. I’ve thought a lot about what we should do to take SUMO to the next level, something I playfully called ‘SUMO 2.0′ when discussing this with the team at the Summit.” David has written five posts outlining the vision for SUMO so far: Part 1: Listen as hard as we can, Part 2: Understanding the bigger picture, Part 3: Increasing community participation, Part 4: Having our finger on the pulse, Part 5: Localization.
If you’re interested in volunteering to help with the SUMO project, you should keep an eye on David’s weblog and read the How to contribute page in the SUMO Knowledge Base. Helping out with user support is a great and easy way to get involved with the Mozilla project.
Polishing Firefox
In an effort to improve the level of Firefox’s visual and interactive polish, Alex Faaborg will be posting a short list of top-priority user experience bugs every Monday morning between now and the Firefox 3.1 launch. He writes, “These bugs will involve fixing some rough areas of Firefox 3’s UI, landing icons that we meant to land before shipping, and trying to make sure every last pixel is perfect.” The team could use some help getting these bugs finished up and closed off, so if you have the time and are interested in helping out, you are encouraged to dive in and get started. Additionally, if there are polish issues you think need to be addressed, Alex asks that you file bugs for those and leave a note in the comments of his post.
Developing guidelines for “Powered by Mozilla”
David Boswell has been working on creating some guidelines to determine how the “Powered by Mozilla” logo can be used as part of projects and products. “Guidelines need to be specific since we don’t want someone to be able to check out just one file from our repositories and then claim that their application is Powered by Mozilla. The problem is that there doesn’t seem to be an existing list of reusable technologies that the Mozilla community creates.” This being the case, David has taken the time to put together draft lists of these technologies and criteria, but is unsure whether the lists are complete or entirely makes sense. He has posted the lists on his weblog, and if you have feedback or suggestions about these he asks that you leave a comment on the blog post or edit the wiki page directly.
Firefox logo style guide progress
As mentioned previously, Tara Shahain and John Slater have been working on a new Firefox logo style guide with the help of the Royal Order and a small team of community volunteers who are acting as an informal panel of advisors. Lots of progress has been made, and Tara has written a new blog post talking about the initial logo inventory (there were 32) and the thought processes that went into narrowing that down to a core set of eight. You can read Tara’s post over at her weblog and join the discussion there.
JavaScript benchmark quality
While JavaScript engine performance has been undergoing a renaissance, JavaScript benchmark tests haven’t been keeping pace and aren’t adapting well to the rapid performance increases we’ve been seeing. John Resig has put together a post analysing the problem, looking at three different benchmark suites — SunSpider, Dromaeo, and V8 Benchmark — and what they are doing to counter-act the problem of error levels increasing as browsers are able to run the tests more and more quickly. It’s a detailed and interesting peek into the world of JavaScript benchmarking, and you can read John’s full post on his weblog.
Managing in/with/around/by chaos
John Lilly recently gave a talk at Stanford about Mozilla’s structure and decision-making processes. “[I]t’s about how Mozilla is organized, and how we push decision-making to the edges of any organization we have — it’s really an organization design and behavior talk.” The presentation is an interesting look into the thinking and blended system of chaos and order behind Mozilla. John has posted his slides over on Slideshare, which you can view here: Stanford Presentation on Mozilla.
Ars Technica on Firefox, Gecko, and WebKit
Ryan Paul of Ars Technica posted an interesting two-page article last week explaining why Mozilla remains committed to Gecko while WebKit popularity is increasing. As WebKit has been adopted by more browsers, Ryan writes, “some technology enthusiasts are beginning to wonder if the days are numbered for Mozilla’s Gecko rendering engine.” This is not at all the case, however, and “those who understand the differences between the two rendering engines and have an appreciation of Gecko’s technical strengths recognize that there is no basis for speculation about the possibility of Mozilla adopting [WebKit] for future versions of Firefox.” In the article, Ryan discusses WebKit’s strengths, why Apple opted for WebKit over Gecko in 2003, how Gecko has evolved and improved since, why Gecko is preferred by a host of third-party developers, and more.
In writing the article, Ryan spoke with Mike Shaver, Mozilla’s VP of Engineering. “Although [Shaver] respects the technical achievements of WebKit, he believes that the WebKit development model and fragmentation in the WebKit ecosystem would create serious challenges that make it unsuitable for Firefox.” Shaver goes into much more detail in the article, which you can find over on the Ars Technica site.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
In this issue…
Add-on Developers: Tell us what you think
If you’re a Firefox add-on developer, please consider taking this brief survey to help us improve the experience of developing and hosting add-ons through documentation, tools, and features. All responses are anonymous and will be read. Take the survey.
AMO Roadmap & Direction
Basil Hashem, Mozilla’s Director of Add-ons, has published some slides on the addons.mozilla.org Roadmap and Editor Community. You can check them out at his blog.
Extend Firefox 3 winners announced!
The winners of the Extend Firefox extension competition for Firefox 3 have been announced. The grand prize winners of Best New Add-on were Pencil, Tagmarks, and HandyTag. The Best Updated Add-on grand prize winners were Read it Later, TagSifter, and Bookmark Previews. The Best
Music Add-on was Fire.fm. You can see a list of all winners and runners up at the announcement post.
Extensions for Fennec (Mobile)
The Add-ons Manager in Fennec is coming along, and Mark Finkle made a post explaining some important things add-on developers will need to know for developing Fennec extensions.
Upcoming Toronto MozCamp/Developer Day
Mozilla is hosting a Developer Day in Toronto on September 15 & 16. Check out Mark Finkle’s post for a description of the event, or take a look at the schedule and sign up if you’ll be able to attend.
Mozilla Labs announces Ubiquity
Ubiquity, “an experiment into connecting the Web with language”, was announced by Mozilla Labs and a prototype Firefox extension is now available. Read the announcement and try it out!
Subscribe
Haven’t subscribed to the about:addons newsletter? Sign up here!
If you’ve developed or tried to develop an add-on for Firefox (or other applications), we’d like your feedback to know what we can do to improve that experience through documentation, tools, and features. Please take a few minutes to complete our survey. Your responses will be anonymous, and every response will be read. We’ll summarize the findings in a few weeks.
Thank you.
In this issue…
Firefox 3.1 Alpha 2 now available
The second alpha version of Firefox 3.1 is now available for download. Firefox 3.1 Alpha 2 is built on a pre-release version of the Gecko 1.9.1 platform, and it is important to note that this release is intended for developers and testers only.
Firefox 3.1 Alpha 2 introduces several new features to the browser, including: support for the HTML5 “video” element, initial support for web worker threads, support for dragging and dropping tabs between browser windows, a new selector to create areas of Aero-style “glass” in XUL, support for new CSS 2.1 and CSS 3 properties, and performance improvements and new preference values for color management profile support.
Please note that this alpha release of Firefox 3.1 does not include the new TraceMonkey JavaScript engine — TraceMonkey is available in nightly builds and is currently disabled by default. For more information, see the TraceMonkey wiki page.
If you’re planning to download and test Firefox 3.1 Alpha 2, you should first read the release notes and the Firefox 3.1 for developers article. More information and download links are available in the DevNews release announcement.
Drag and Drop is here
Neil Deakin has posted a development update about the inclusion of the HTML5 drag and drop API in Mozilla nightly builds. “This is the API that IE and Safari have supported for a while. Now Firefox will support it as well so you can create content in your web pages that can be dragged and dropped elsewhere. The same API is also used for Firefox extensions and XUL applications.” For more information, including examples about how to make things draggable, see Neil’s weblog post. Drag and drop documentation is available at the Mozilla Developer Center.
Mozilla, Firefox and Google Chrome
As most browser-industry watchers know, Google has launched a beta version of a new web browser called “Google Chrome”. John Lilly posted about it at the time, and Mitchell Baker has written about it since, discussing how and why Mozilla and Firefox continue to be unique and vital in an increasingly healthy browser market where competition and innovation are again the norm.
Mitchell writes, “Mozilla exists to build portions of the Internet where individual human benefit, social benefit, and civic benefit are the most important things. [We] recognized long ago that an independent browser dedicated only to the public good is a necessary piece for building a healthy internet. Firefox is our first step in building that Internet. Clearly we need to continue to build great products, and to lead in a competitive market. Mozilla created this competitive environment through the success of Firefox, and I’m as confident as John is about Mozilla’s future.”
“We’ll continue to compete in the browser world, and we’ll continue to do well. We’ll continue to produce a product that people choose and trust and understand is theirs. We’ll continue to do this as part of our overall mission — building an Internet where individual, civic and social value are paramount.” Read Mitchell’s full post on her weblog.
Andreas Gal on the TraceMonkey JavaScript engine
For the past two months Andreas Gal has been working with the Mozilla team creating a just-in-time (JIT) compiler for the JavaScript engine in Firefox. On August 22nd the project (code named “TraceMonkey”) was added to the main Firefox development code base.
Andreas writes, “TraceMonkey is a trace-based (.zip PDF) JIT compiler and it pushes the envelope on JavaScript performance. On average, we speed up Apple’s popular SunSpider benchmarks by a factor of 4.6 over the last release of Firefox. For the SunSpider ubench suite, which focuses on core JavaScript language features, we achieve a speedup of 22x. Whichever metric you chose to apply, Firefox now has the fastest JavaScript engine in the world.” Andreas’ post goes on to discuss the concepts and background behind TraceMonkey in detail, including dynamic compilation with traces, trace trees and nested trace trees, and type specialization. You can read the full article at Andreas’ weblog.
TraceMonkey vs. V8: JavaScript performance
JavaScript is an increasingly vital aspect of web browser performance since many web applications (web mail, online word processors, and so forth) rely heavily on complex JavaScript programs for their core functionality. In the past year, JavaScript performance has gone through somewhat of a renaissance, with massive strides being made by JavaScript developers working on several different projects. The two most recent developments come from Mozilla and Google — Mozilla’s new TraceMonkey engine that is part of Firefox 3.1 development, and Google’s new V8 engine that is part of the Google Chrome beta.
Brendan Eich has run some performance tests, and has posted the results of the head-to-head showdown in which he pitted the engines against each other using the SunSpider test suite on Windows XP and Windows Vista (Google Chrome is not currently available for either Mac or Linux). Brendan writes, “[TraceMonkey] win[s] by 1.28x and 1.19x respectively,” but adds that SunSpider is “one popular yet arguably non-representative benchmark suite.” He finishes by pointing out that “this contest is not a playoff where each contending VM is eliminated at any given hype-event point,” going on to sketch the rough outlines of the approach the team is taking to further improve TraceMonkey performance.
Brendan’s complete test results and commentary are available on his weblog. Further information about TraceMonkey and JavaScript performance is available through web posts by Mike Shaver, Andreas Gal, and John Resig.
Mobile Firefox, now with add-ons
The recent release of Fennec (the code name for Mobile Firefox) Milestone 7 included the revolutionary addition of an Add-ons manager for the mobile browser. Mark Finkle has written a detailed post that talks about developing add-ons for Fennec, explaining its various similarities and differences to Firefox. “Fennec is a XULRunner application and gives extension developers access to the same underlying XPCOM system that is used in Firefox. The process of building extensions is the same as for any other Mozilla based application.”
There are significant differences, as well. “Fennec is not Firefox. It is a completely different application. Fennec’s UI is also very different than Firefox. This means you can’t just plop a Firefox (or Thunderbird or Songbird) extension into Fennec and expect anything to work. There are some basic things an extension developer will need to handle when making or porting extensions to Fennec.” These differences include: a different application id, a very different XUL UI, and different JavaScript objects and functions in the UI code, among other things.
Mark suggests that currently the best way to figure out what’s available is to look at the source code. If you have questions, jump into Mozilla IRC’s #mobile channel, and someone there should be able to help you out. Mark also includes some example Fennec extensions, which you can find linked in his blog post.
Designing a theme for Mobile Firefox
Madhava Enros and Sean Martell have been working on creating a default theme for the Fennec web browser (”Fennec” is the code name for Mobile Firefox). Madhava writes, “We’re trying for something that nods back in the direction of Firefox on the desktop while still striking out in a direction that’s appropriate for a small-screen finger-directed device. [Sean]’s posted some recent work to his blog, and he’ll be posting more there as we go. This is an effort still very much in progress, so please jump in with your suggestions. There’s a Fennec UI discussion thread ripe for contribution.” For more information and some mockups of the theme, see Madhava’s blog post.
Language-based interfaces
Jonathan DiCarlo has been writing a series of blog posts discussing language-based interfaces — interfaces that allow you type commands in real language and the right stuff happens. “What would the web be like if you could tell it what you want to do as easily as you currently tell it where you want to go?”
Mozilla Labs has started experimenting with linguistic interfaces that are designed to do just that, the first of which is the recently-launched Ubiquity project. Jonathan’s posts are an extensive look into the concepts, questions, and thinking behind the experiments, and he has written three so far — Language-based interfaces: The problem, Language-based interfaces: Where do we stand now?, and Language-based interfaces: Report card for Ubiquity. If you’re at all interested in these approaches and ideas you should read Jonathan’s blog then head over to the Ubiquity project to get involved with the growing community working on these experiments.
Upcoming events
Toronto, Sep 15-16, MozCamp: Two-day developer event full of talks, tutorials, and workshops. See the Toronto MozCamp wiki page for more information.
Paris, Sep 20, Add-ons workshop: A one-day event to bring together French-speaking XUL developers, hackers, and Web developers to discuss Mozilla technologies. See the Mozilla wiki MAOW page for more information.
Barcelona, Oct 25-26, MozCamp: A large, two-day Mozilla conference being held in Barcelona on the weekend of Oct 25-26, 2008. See the Mozilla Camp Europe wiki page for more information.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
The second developer milestone of the next release of Firefox - code named Shiretoko Alpha 2 - is now available for download. Shiretoko is built on pre-release version of the Gecko 1.9.1 platform, which forms the core of rich internet applications such as Firefox. Please note that this release is intended for developers and testers only.
This Alpha of Shiretoko / Gecko 1.9.1 introduces several new features:
Anyone interested in Shiretoko should read the release notes, as well as the “Firefox 3.1 For Developers” article on the Mozilla Developer Center before downloading. Please use the following links to download Shiretoko:
We would appreciate hearing about any feedback you have, or any bugs you may find.
(Those interested in testing Mozilla’s new JavaScript engine “Tracemonkey” should note that it is not included in this development milestone. If you’re interested in that technology, please obtain a nightly build and follow these instructions)
In this issue…
Introducing Ubiquity
Mozilla Labs introduced the Ubiquity project last week, an “experiment into connecting the Web with language in an attempt to find new user interfaces that could make it possible for everyone to do common Web tasks more quickly and easily.” Alongside the announcement, Labs also released an early experimental prototype that demonstrates some of the concepts behind Ubiquity. You can install the prototype, read the tutorial, and learn more about Ubiquity in depth. Further information is available at the Mozilla Labs announcement and Aza Raskin’s weblog.
John Lilly: Thoughts on Chrome and more
John Lilly, Mozilla’s CEO, writes, “Interesting developments in the browser world lately. Between the new beta of IE8 and Google releasing the beta of their new browser (called “Chrome”), not to mention interesting work by the Mozilla team here as well, there’s as much happening as I can ever remember. Let’s start from there: more smart people thinking about ways to make the Web good for normal human beings is good, absolutely. Competition often results in innovation of one sort of another — in the browser you can see that this is true in spades this year, with huge JavaScript performance increases, security process advances, and user interface breakthroughs. I’d expect that to continue now that Google has thrown their hat in the ring.”
Lilly goes on to discuss how the release of Google’s “Chrome” project affects Mozilla, what this means for Mozilla’s relationship with Google, and how Mozilla continues to be unique in the browser world. “Mozilla’s mission is to keep the Web open and participatory — so, uniquely in this market, we’re a public-benefit, non-profit group (Mozilla Corporation is wholly owned by the Mozilla Foundation) with no other agenda or profit motive at all. We’ll continue to be that way, we’ll continue to develop our products and technology in an open, community-based, collaborative way.” Read the full post at Lilly’s blog.
Mobile Firefox “Fennec” Milestone 7 released
The Mozilla Mobile team has announced their latest release. “Fennec (Mobile Firefox) has reached milestone 7 (M7) and can be installed on a Nokia N8×0 for testing. We got some good feedback (and bug reports) from M6, so there are more than a few bug fixes in M7. Other additions include better add-on support, initial kinetic scrolling, modeless password manager, and some zooming tweaks. Please take Fennec M7 for a spin and file some bugs.” The Mobile team has posted install instructions and the M7 Readme, and you can read the full release announcement at Mark Finkle’s weblog.
Thunderbird “Shredder” Alpha 2 released
Mozilla Messaging announced the release of Thunderbird “Shredder” Alpha 2 on August 12th. “Shredder Alpha 2 is a developer preview release for the next major version of Thunderbird that is built on top of the next generation of Mozilla’s layout engine, Gecko 1.9. Shredder Alpha 2 is being made available for testing purposes only and is intended for developers and our testing community. This release does not represent the final product. Some of the features are highly experimental and will likely change before final release. Please do not use Shredder Alpha 2 in a production environment.” For more information, including further release details, a list of features and enhancements, FAQs, and download links, please see the Shredder Alpha 2 Release Notes.
Mozilla and certification authorities
Frank Hecker writes, “Johnathan Nightingale recently addressed a very common question, namely why Firefox doesn’t automatically accept self-signed SSL certificates as being valid. I don’t have much to add to Johnathan’s discussion of the issues with self-signed certificates, but speaking on behalf of the Mozilla Foundation I do want to address some of the comments that I’ve seen people make with regard to SSL certificates, certification authorities (CAs), and Mozilla.” Frank’s blog post discusses some of the misconceptions related to Mozilla and CAs, debunking some of the more commonly repeated myths that exist around this topic.
Defining Firefox logo style
John Slater and Tara Shahain have been working on developing a new and improved style guide for the Firefox logo. The goal is to refine the existing guidelines and to get those communicated out to the widest possible audience. As part of this project, John and Tara gave a talk at the recent Firefox Plus Summit, and have started working with the Royal Order on creating the guide. They also very much want to keep the process as open as possible, so John will be blogging about various topics for discussion over the next few weeks. Additionally, they have assembled an informal advisory panel for the project, drawing upon the expertise and experience of several veteran members of the Mozilla contributor community. For more information, including a list of the people who are on the advisory panel, see John’s blog post.
Upcoming Events
Barcelona, Oct 25-26, MozCamp: A large, two-day Mozilla conference being held in Barcelona on the weekend of Oct 25-26, 2008. See the Mozilla Camp Europe wiki page for more information.
Paris, Sep 20, Add-ons workshop: A one-day event to bring together French-speaking XUL developers, hackers, and Web developers to discuss Mozilla technologies. See the Mozilla wiki MAOW page for more information.
Toronto, Sep 15-16, MozCamp: Two-day developer event full of talks, tutorials, and workshops. See the Toronto MozCamp wiki page for more information.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
In this issue…
Firefox 2 gets a major update
Starting yesterday evening, users with the latest version of Firefox 2 will receive an automated offer to update to Firefox 3. If you’re running Firefox 2.0.0.17 you will see the offer in the next couple of days, but if you’re eager you can always “Check for Updates” in the “Help” menu. The Firefox team has posted extensive details about this update over on the Mozilla Developer News weblog if you would like more information.
Monthly Labs Meetup - Thurs, Aug 28 in SF
Rhian Baker writes, “It’s time for another Monthly Meetup. This month’s meetup will be Thursday, August 28th, 6pm at the Twitter office — 539 Bryant St. Suite 402, San Francisco. There will be progress updates on the various active Labs projects as well as plenty of opportunity for discussion and hacking. And, of course, pizza. If you are in the Bay Area, we’d love to see you!” If you’re planning to attend, please take a moment to RSVP by commenting on the Mozilla Labs weblog.
Toronto MozCamp: Workshops - Sep 15-16
Mark Finkle has posted more information about the upcoming Toronto MozCamp that is being held on September 15-16 at Seneca College. “We decided to use the second day as a ‘Hands-on Workshop’ day. The workshop will be split between development and testing tracks.” The development track will be run by several Mozilla developers who will help participants work on tutorials and projects, and there will be some XUL applications, extensions, and XPCOM components for people to hack on. The testing track will be covering topics related to Mozilla’s testing processes, including how to write unit tests and how we automate testing of Firefox. Clint Talbert has more information about this workshop.
Mozilla Camp Europe - Oct 25-26
Mozilla Europe has announced Mozilla Camp Europe, a large two-day Mozilla conference that will be held in Barcelona on the weekend of October 25-26, 2008. “The aim of the event is to bring together Mozillians from three main areas: Development, Localization and QA. The event will be held at Citilab in Barcelona and we hope to have enough places to invite 150 community members from across Europe.” For more information, see the Mozilla Camp Europe wiki page, which includes a tentative schedule, tracks, and other details. The Mozilla Europe team will post further information on William’s weblog and the wiki page as it is available.
Mark Surman: New Mozilla Foundation Executive Director
After a long and extensive search, Mitchell Baker has announced that Mark Surman will be joining the Foundation as the new Executive Director. Mark has also posted about this move, writing, “I am totally psyched about this. Mozilla is a new kind of foundation, one with participation, transparency and innovation at its very roots. It’s not just about giving out grants or making bold statements (although these are useful things to do), but also about getting large numbers of people involved in making things. In particular, things that make the Internet more open. For someone obsessed with reinventing how foundations work, there could be no more exciting job than this.” Mark will be officially starting his work with the Mozilla Foundation on September 22nd, 2008.
New Mozilla Web Tech weblog
Keeping track of Mozilla development is never easy, especially the minute details related to new or improved web technology development and support. The Mozilla development community has set up a new “Web Tech” weblog to help fix this. There, Mozilla developers will be posting about and discussing topics of interest to web developers. For example, recent posts include: word-wrap: break word support, CSS 2.1 generated content, and querySelector[All]. Questions and discussions are welcome, so check out the weblog and stay up to date on all the latest Mozilla web technology.
New and improved Mozilla Developer Center
Last week, the Mozilla Developer Center switched from using MediaWiki to being powered by MindTouch Deki, a huge task that’s been underway since late last year. The new site has a user-friendly WYSIWYG editor, an easier to work with scripting system for customizations, software that’s much easier to maintain, and a polyglot solution that allows all the localizations to live in a single wiki. The team is also working directly with MindTouch to add features so Deki will fit MDC’s needs even better. If you’re interested in further developments, you should watch Eric Shepherd’s blog and the dev-mdc newsgroup.
JavaScript performance improvements coming for Firefox 3.1
Mike Shaver writes, “Over the past year, JavaScript performance on the Web has undergone a striking revolution. Virtually every browser has improved its engine to produce significant gains in execution speed; Firefox 3 is about 3 times faster than Firefox 2 in various JavaScript benchmarks, for example. We’re not done. In addition to continuing to work on our existing JavaScript interpreter, we’re also looking farther into the future of JS performance. Yesterday we landed TraceMonkey in the Firefox 3.1 development tree, [and] we’re charging full speed ahead on the work we need to do for this to be part of Firefox 3.1″. Early tests are showing significant speed and performance improvements. TraceMonkey has been blogged about at length by the various people involved:
Firebug 1.2 released
The final version of Firebug 1.2 has been released and is available through the Mozilla Add-ons site and GetFirebug.com. There have been a huge number of improvements and bug fixes made, including the addition of Firefox 3 support, quality improvements, selective panel enablement, and the ability to suspend/resume the add-on. Additionally, Firebug 1.3 development is already underway and will be focused on performance, quality, and testing. For more information, see John Resig’s blog post announcing the Firebug 1.2 release.
Extend Firefox 3 contest winners
Extend Firefox 3 — the contest in which participants submitted new or updated add-ons for the Firefox 3 web browser — has wrapped up and the winners have been announced. Many of the winning add-ons are in the early stages of experimental development, but all are powerful new tools and prototypes that the judges felt were worthy of recognition. For the list of winners and further details about the contest, please see the Mozilla Labs weblog.
Firefox Mobile design session: bookmarks
Aza Raskin writes, “For the third installment of the Firefox Mobile design discussions, it’s bookmark time. Bookmarks have been a fundamental feature in the browser since Mosaic days. Do they have a place in Mobile? Are there better paradigms? How are they displayed? What’s the difference between a tab and a bookmark? Is it only a matter of one being in the device’s memory?” These are some of the questions that are asked and answered in the third video installment of the Firefox Mobile design sessions. The team looks forward to your thoughts and feedback. More information is available at Aza’s weblog.
Developer calendar
For an up-to-date list of the coming week’s Mozilla project meetings and events, please see the Mozilla Community Calendar wiki page.
Subscribe to the email newsletter
If you would like to get this newsletter by email, just head on over to the about:mozilla newsletter subscription form. Fresh news, every Tuesday, right to your inbox.
Starting a little later tonight, users with the latest version of Firefox 2 will be getting an offer to update to Firefox 3. If you’re running Firefox 2.0.0.17 you will see the offer in the next couple of days, though if you’re eager you can always “Check for Updates” in the “Help” menu. This is what the offer will look like:

Clicking the “Learn More” link will open a new tab with more information about Firefox 3 to help you make your decision about upgrading. From there, you have a choice:
Some of