As I said, though, we’ve been working on all sorts of things so far this year. Dan Weber has been hard at work on patches for some of the most visible issues with the new autocomplete experience, and I landed the fix for the magically-reappearing autocomplete window tonight. Dan is also still working on improving the speed of autocomplete for large histories, though that patch is not yet ready. Chris Lawson has also been working on various and sundry other bugs, including changes to the Flashblock exceptions list so that pasting URLs into the field will work as users expect. Philippe Wittenbergh is hard at work polishing some of our toolbar icons.

Christopher Henderson has been working on a patch that moves our history off of Mork, which is both the sane thing to do and critical for moving forward to the new Mork-less world. As usual, I have been chasing down bugs here and there and wrangling patches to get ready for the upcoming 2.0.2 and 1.6.11 releases. We’ve also seen Alex Jones, who has been working off-and-on on supporting Mobile Me sync, again recently, though it sounds like Sync Services wants to do things in a manner that is not easily compatible with Camino’s bookmarks implementation. All in all, we’ve been fairly productive since the new year began.

Which brings us back to the title of this post and to this weekend’s developments. Late Saturday afternoon, I got a debug version of Camino to build, launch, and run using Gecko 1.9.1, and early Sunday evening I was able to make a static (i.e., distributable) build do the same thing. (Even better, Christopher Henderson was able to replicate my success.) This feat would not have been possible without all the hard work that Christopher put in for the aforementioned history migration, as well as a good bit of debugging and patching he did this weekend as we hit some unexpected code-change-related build failures. After applying those patches, I mostly deleted and added things to the project and waited for the next build failure. At the end of the day, though, Camino launches and runs, plays <audio> and <video> (with Ogg), and displays pages with @font-face (with raw TrueType fonts).

This doesn’t mean that we can turn around and release a version of Camino based on Gecko 1.9.1 (and there’s a very strong possibility we may not); for starters, there are a number of known regressions (including the loss of Find-As-You-Type), as well as possibly hundreds of other serious problems we haven’t discovered in our limited test browsing. Beyond that, the “build system” is not yet a system at all; it involves pulling mozilla-1.9.1 from hg, checking out Camino from cvs into mozilla/camino, and applying a large patch. But if you’re brave or crazy, you can try this at home now (and for those less brave or more sane, there’s an Intel-only build here that you can use to help us find other broken things. N.B. You should treat this build as highly experimental. It might eat all of the cheese in your house. It will eat your profile, so make a backup copy first).

We also know (thanks to earlier attempts by Philippe Wittenbergh and Kai Rune Mathisen to build mozilla-central) that there are more serious code breakages in newer versions of Gecko, so this is only the beginning. In between other things the last few weeks, I’ve also been working on a new repository and fleshing out issues and solutions for the build system. There’s a long road ahead, and Camino 2.1 might be ready before we’ve gotten to the end of the road; we’ll have to see. However, as Christopher said on Saturday night, “it’s been a great day in Camino Land.”

This news is a bit old now (since it appeared briefly on Planet Mozilla the other day half-buried in a PR round-up, and since reader James reported it in a comment on January 21), but FCKEditor is the winner of the 2010 edition of the annual “we break our site for your browser when the new year rolls around” broken browser-sniffing contest.

If you use FCKEditor on a site and it doesn’t work with Firefox 3.6 or nightly builds of any Gecko browser built since January 1, you’re probably seeing the bug that won FCKEditor this year’s prize with a stunning upset of two-time defending champion Yahoo!

My gut feeling is that this new type of contest winner is much worse than the old “major site is broken” type, since there is no single point of contact for the fix (everyone who uses the affected versions of FCKEditor will have to patch or upgrade their install), since unpatched instances of FCKEditor could break functionality on websites far and wide for years to come, and since in some ways the distributed nature of the problem means there is less visibility than when a major website suddenly ceases to work correctly.

I think this also highlights the importance of web “library” or “component” authors doing things correctly from the beginning—not browser sniffing at all, but instead testing for features—because their code will be used widely and, as I understand it, they have little control over getting consumers to update when there are fixes for broken things like this.

If you’re going to write something for wider consumption, or that you think may one day be useful to large audiences, please take the time to get things right from the beginning, especially if your code doesn’t have a dead-simple upgrade experience. Your users, and their users, and even other unrelated software vendors, will thank you for it later.

(And remember: only you can prevent broken browser sniffing! )

1. First and foremost, we released Camino 2, a significant new release with lots of great new features like Tab Overview, phishing and malware protection, drag-and-drop rearranging of tabs, Growl support, and new AppleScript features. As with all community projects, it took longer than anticipated, but based on the very positive reaction, it was well worth the wait.
   • Stuart Morgan fixed the most bugs, while Sean Murphy wrote three major new features; Jeff Dlouhy, Christopher Henderson, and Ilya Sherman also contributed major features to Camino 2.
   • Our localization teams stayed busy, so the Multilingual edition of Camino 2.0.x currently ships with 15 languages.
2. In conjunction with the Camino 2 release, we rolled out a redesign of caminobrowser.org. Thanks to our friends at Clearleft for the design work, Samuel Sidler for implementing the redesign, and Philippe Wittenbergh for helping to polish the rough edges afterwards.
3. While our focus was on Camino 2, we continued to release security and stability updates for Camino 1.6 throughout the year, and beginning in the summer we started landing code for what will become Camino 2.1.
4. Dan Weber was our Google Summer of Code student in 2009, working on enhancing the location bar. Over the course of the summer, Dan implemented a new look for the autocomplete window as well as extending autocompletion to include URLs and titles of both bookmarks and history items (fixing a couple of the oldest remaining Camino bugs in the process). Check out a nightly build to see his work in action.
5. Our hard-working localization teams added two new languages this year, Slovenian and Turkish, and revived two translations, Chinese (Simplified) and Danish that have been missing for several major releases. Sadly, a few languages didn’t make the jump to Camino 2, so if Camino is not currently available in your language, drop by the caminol10n project website, join the mailing list, and learn how you can help!

I think that about wraps up the high points of the year, in a little briefer fashion than years past. Thanks to everyone who was a part of the Camino community in 2009—developers, testers, localizers, and users—for a great year! We’re always looking for new contributors, so if you’d like to help make Camino even better, there are many ways you can help out in the coming year. In the meantime, enjoy Camino 2, Happy New Year, and welcome to 2010!

As I noted in January, the “three-peat” is Yahoo!’s to lose, although there was some talk last January of Yahoo! actually doing away with their date checking.

Get your picks in now for both the site/company that will break and the reporter of the Tech Evangelism bug who notices said site/company. (For the record, my picks are Yahoo! and Philippe Wittenbergh.) No actual prizes will be awarded, but both winners will be recognized in a future entry in this journal.

And remember: only you can prevent bad browser-sniffing!

• Stuart Morgan handled the major Camino code changes for 2.0.1. He got Mac OS X 10.6 and the Help menu talking again in non-English localizations, and he hooked up support for collecting emails in the Camino Crash Reporter (once email addresses are available for authorized users of crash-stats, we’ll be able to contact you for more information about your crashes when we need your help).
• Christopher Henderson wrote a patch to make the about:config context menu start working, which is handy now that we officially acknowledge that about:config exists. He has also been working on some history-related changes and on implementing some missing bits in CocoaPromptService that the about:config context menu wants to use.
• Chris Lawson gave Christopher’s patch a review, and he also began working through our backlog of unconfirmed bugs, following up on those that haven’t seen activity for a while.
• Samuel Sidler and Philippe Wittenbergh have been polishing some of the slightly-rough edges of the new website design and doing their usual parts to help with bug triage.
• With the release work for 2.0.1 out of the way, I’ve also joined in on the website polishing and bug triaging. Mostly, though, I feel like the sprint to 2.0 and then 2.0.1 is finally done, so I can take a moment and breathe.

That’s it for now; we’re slowly getting back in gear for the road to Camino 2.1, but the number of exciting changes will probably be light until after the new year.

The road to Camino 2 began in April of 2008 when we wrapped up work on Camino 1.6, although we had been performing architectural maintenance and related work to keep up with Gecko 1.9 changes since late 2007 (and some of the changes in Gecko itself were made all the way back in 2005, after the MOZILLA_1_8_BRANCH was cut on August 12, 2005). Over the last year and a half, we’ve fixed more than 450 “bugs” (problems or new features), and 16 different people contributed patches for this release (Stuart Morgan again led the way with 119 fixes). Sean Murphy implemented three major features this release (tab dragging, phishing and malware protection, and rewritten Full Keyboard Access support in the browser window), and Christopher Henderson and Ilya Sherman showed up to implement full content zoom and Growl notifications for downloads, respectively, and stuck around to fix over four dozen other bugs between them. Big thanks also to the one-third of that list of patch contributors who aren’t regular Camino developers; every little fix helps make Camino a better browser.

In some ways Camino 2 isn’t the revolutionary release we hoped it would be when we wrapped up Camino 1.6, but it’s still a vast improvement over Camino 1.6 and a triumph for an all-volunteer, all-free-time development team in today’s world of corporate-sponsored browsers.

Thanks to our hard-working localization teams, Camino 2 is available today in US English and 13 other languages, with Polish expected to join that list as soon as our Polish localizer’s Mac is repaired. Sadly, we had a few languages that shipped in Camino 1.6 disappear on us, so if your language is missing, please stop by the caminol10n mailing list and see how you can help bring these localizations back. (As I mentioned earlier this year, the work doesn’t require much specialized computer/software knowledge; you and a friend can bring Camino to thousands of users in your language! For Camino 2, new contributors successfully revived the Danish localization, which was in Camino 1.0 but disappeared from Camino 1.5.)

This year I again went to bed the night before release while fearless webmaster Samuel Sidler stayed up putting the finishing touches on the home page, the Features page, and implementing the new website design from the folks at Clearleft. One of these years both Sam and I are going to get a full night’s sleep before a major release, but this was not to be that year. Aside from a few things here and there, it seems like the website and webserver bits went more smoothly this release than with 1.6.

What’s next? Those of us who have been working on the website and release details for the past month or so are going to take a little rest. Parts of the development team, which wrapped up development with a late-October push, are already starting to work on new features for Camino 2.1. Nightly builds already include Dan Weber’s 2009 Summer of Code work on location bar autocomplete, and we have some early plans for other features in Camino 2.1 (we’re always looking for contributors, so if you’re interested in helping make a great Mac browser, stop by the Contribute page or find us on irc).

In the meantime, enjoy Camino 2.0 and let us know what you think!

I have some good news and some bad news about these crashes. The good news is that we’ve been looking at the problem for a while now, and Mozilla’s font gurus, John Daggett and Jonathan Kew have a couple of theories about the cause of the crashes (probably Mac OS X font cache corruption, yay! ). In addition, we generally know how individuals can “fix” the cause of the crashes on their own Macs.

The bad news is that the individual “fix” so effective that we aren’t currently in contact with anyone who is still experiencing this problem, and reversing the “fix” doesn’t cause the crash to reappear. This makes it much more difficult to determine what exactly is wrong and to find the best way to fix the Mozilla code to make whatever the underlying problem is not crash Camino, now or in the future, for everyone.

If you’re currently experiencing this crash, we could use your help. There are questions in need of some answers, and we’ll probably be able to generate some test builds (to log additional information and eventually to test proposed fixes) soon. Please comment in bug 514114 if you’re seeing this crash. (If you can’t get Camino to launch in order to check about:crashes for your crash ids, you can open the Camino inside the Breakpad folder inside the Library folder in your users’s Home folder and look for files with names in the format of CrashID=bp-0c24401b-93b6-4f7e-bcf7-8e4062091108.dmp; paste the bp-0c24401b-93b6-4f7e-bcf7-8e4062091108 part into the search field on crash-stats to find your report.)

Finally, if you just want to make the problem go away and can’t help us track down the cause of the crash, you should open Font Book, check for and resolve any duplicate fonts (in the Edit menu), and validate all of your fonts, removing any ones that Font Book flags as having problems (in the File menu). You may also need to restart your Mac after removing duplicate and corrupted fonts.

Thanks for your help investigating this crash; we hope we’ll soon be able to make Camino stop crashing for everyone who is, or will be, experiencing this problem on Mac OS X 10.6.

Update (2009-11-17): John came up with a patch that should fix the crash, and it was reviewed and approved this evening. The fix should appear in tomorrow’s (2009-11-18) Camino 2.0.1pre, 2.1a1pre, and Firefox 3.0.16pre nightly builds.

Like Talkback before it, the Breakpad-based Camino Crash Reporter collects data about your crash and, when you agree, sends the data to Mozilla servers, where we (the Camino team) get to see the information in aggregate (and non-personal information in individual crash incidents).

How crash reporting works in Camino 2

If Camino crashes, the Camino Crash Reporter pops up and asks you to add a comment and then to report the crash:

When you restart Camino, you can visit about:crashes to find the report ID for the crash you just experienced and even see the processed report.

The about:crashes page contains a list of report IDs for crash reports you’ve submitted successfully to Mozilla’s crash collection servers. If you click on the report ID, you can see the processed report for your crash. Not all reports are processed immediately, so you may see a “processing” screen at first:

Once processing is complete, you can see the full report for your incident on crash-stats:

How you can improve the chances of your crash being fixed (and how to improve your crash report)

We hope that you’ll never have to use the new crash reporting in Camino 2, but if you do, following these simple steps will make your report as useful as possible and improve the chances of the crash you experienced getting fixed.

When you experience a crash, the most important thing you can do is to allow the Camino Crash Reporter to submit your report to us. If we don’t know a crash is happening, there is a zero percent chance that we will be able to fix it (if you’re happy seeing the same crash over and over, then don’t feel the need to submit a crash report ). Many times we’re able to discover and fix crashes just from the aggregate data generated from users submitting crash reports to us.

Second, when you submit your report, please add a comment! We know that crashing is frustrating and disrupting, and it is tempting to just press Submit (or even Cancel) and get back to what you were doing. However, while the computer-generated data that is submitted in the crash report tells us “what” is happening, it often is insufficient to allow us to fix the problem, and comments can help bridge that gap. When you add a comment, please be reasonably descriptive when telling us what actions you might have performed just before Camino crashed. As you can see in the sample crash above, I listed a number of specific steps that I performed just before Camino crashed.

In addition to providing a comment, if you are comfortable providing the URL you were viewing when Camino crashed (and you know, or can look up in History, what that URL was), include it in your comment, too. While Camino attempts to collect the URL you were on when Camino crashed, the URL is not displayed with your crash report for privacy reasons and is not readily available to anyone. As I mentioned several years ago, a good comment and a URL can be the difference between a frustrating crash and a fix. Unfortunately, only a few reports out of every hundred currently include a comment, so there are many opportunities to understand and fix crashes that are currently being lost.

Finally, if you experience what you think might be the same crash, over and over—either whenever you visit a certain site you crash, or performing the same series of actions on a variety of sites leads to a crash—please file a bug. While aggregate crash data can help us discover crashes, especially those that don’t otherwise seem to have a pattern, this data is no substitute for a bug report from someone who is actually seeing the crash frequently. Sometimes specific crashes can still get lost in aggregate data, and filing a bug report on a crash that’s plaguing you can bring it to our attention.

When you file your bug report, please be sure to include the report IDs of incidents of this crash. To get the report ID, type about:crashes in Camino’s location bar and press Return. Camino will display a list of crash reports you have submitted and their corresponding report IDs (a long string of letters and numbers). Copy the crash report ID corresponding to the crash you are reporting and paste the ID into your bug report, adding bp- to the beginning of the pasted string. For example, a crash report id of 0c24401b-93b6-4f7e-bcf7-8e4062091108 should become bp-0c24401b-93b6-4f7e-bcf7-8e4062091108 in your bug report, and Bugzilla will then link that string to your crash report. (Please do not paste entire crash reports into the “Comments” field of the bug report.) Then, please be willing to answer questions and perform some tests as we work to understand and fix the crash you’ve reported in the bug.

Finally, when filing a bug or making a comment in a crash report, please don’t berate us. We know you’re upset that Camino crashed on you, and we’re just as upset, but yelling at us doesn’t help. Also, since at least one-third of crashes we see are caused by third-party software (for example, browser plug-ins, third-party hacks, or even fragile parts of Mac OS X itself), you might be yelling at the wrong party anyway.

In summary:

1. Any crash report you submit is better than no report at all, so please always allow Camino Crash Reporter to do its job.
2. The more information you provide in your crash report (comment or URL), the more useful your report is to the developers.
3. For crashes you can reproduce or see over and over, reports filed with Camino Crash Reporter are no substitute for an actual bug report (with crash report IDs).
4. Please be polite and civil in your comments and bug reports; we’re all working towards the same goal here (Camino not crashing on you).

All of which is a long way of saying “you could be the key to fixing the crash that is annoying you.”

Please enjoy Camino 2 (due out “real soon now”), and don’t fear the Camino Crash Reporter; it’s only trying to help.

Camino 2 is likely going to ship in English and 13 other languages (attentive readers will note that this is down by two from the number of languages in Camino 1.6.10, but still three more than shipped in the initial Camino 1.6 release), all translated by our volunteer localizers from the caminol10n project. New to Camino 2 will be Danish (which last appeared in the Camino 1.0 series) and Turkish, making its debut as a Camino localization.

The story of Danish in Camino 2 is particularly worth telling. At the end of September, about two weeks after we released Camino 2.0 Beta 4, Danish Camino user Allan Nyholm Nielsen posted a message in the Camino discussion forum asking why Camino 1.6 was localized in Swedish and Norwegian but not Danish, and whether Camino 2 would include a Danish translation. A member of the Camino development team replied that our localizations are all produced by volunteers and that while there had been a Danish localization in Camino 1.0.x and some work had been done for Camino 1.5, the leader of that team disappeared and the translation for 1.5 was never finished. We also pointed Allan to the caminol10n project (and to another Danish Camino user on the forum, David Munch, who could possibly help) and urged him to think about reviving the Danish translation.

The very next day, Allan had posted to the caminol10n mailing list (and back in the Camino discussion forum) stating that he had signed up and had gotten started. Two weeks after that, Allan posted a message stating that he had essentially completed the translation of Camino 2 into Danish, and, after a week of polishing the translation, he reported he had the complete translation ready.

In three weeks, we went from having no Danish translation and only an interested user who had never done any Mac OS X application localization to having a complete, peer-reviewed Danish localization for Camino 2.0! Congratulations to Allan and David on this achievement.

If you would like to see Camino in your language, you too can make it a reality. While not every language has a localization of an older version of Camino available to jump-start the process (there are a dozen languages that have shipped in past Camino versions that will not be in Camino 2.0, however), and while some teams take longer to complete a translation than others, you can still get started today and perhaps be ready to include your language in Camino 2.0.1 or 2.0.2. There are a few, relatively simple, specialized tools to learn, but for the most part all you need to know is English and your own language. There might even be other speakers of your language already interested in helping, and the existing Camino translators are knowledgeable and can help you get started with the tools.

The Danish experience is not an isolated case, either; during the Camino 1.6.x series, we added three new languages, and one of them was complete in a matter of weeks (one took a month or so, and the third we learned about only when it was already complete).

If your language is already included in Camino, be sure to thank the members of your language’s translation team and ask them if there is any way you can help; existing teams are usually looking for new members, too, to help spread the workload.

Finally, it is with sadness that I report that Catalan, Czech, Polish, and Portuguese (pt-BR) will be missing from Camino 2.0, so if you are a Camino user who speaks one of those languages, now is the time for you to get involved. Register with the caminol10n project, join the mailing list, and bring your language back to Camino.

I realized tonight that in the year that I have been handling the “build” side of Camino’s build and release process (at first sharing duties with the illustrious Mark Mentovai, and then on my own), I’ve produced builds for a bunch of releases: five Camino 2 milestones and five Camino 1.6.x security and stability releases (with at least one respin in the mix). However, I had never been responsible for the build process for a major release, for the new version that’s all shiny, the culmination of the entire team’s hard work, and the build that’s tested and reviewed by the world. Since 2006 (and Camino 1.0), Mark had always handled that. Tonight, though, I felt the weight of tagging on my shoulders.

Which is a long, rambling, nostalgic way of saying that we now have a Camino 2 release candidate (note to the press and other interested parties: release candidate; Camino 2 is not out yet) for our community to hammer on, with special thanks to Stuart Morgan for fixing a dozen or so of our blockers and wanted/pseudo-blockers in the past two weeks and to Mark for the ninetieth-minute superreview on the very last patch.

I’ll have more to say about Camino 2 in the coming days, and the release will be here before you know it, but for now I’m just going to mark this milestone, point everyone to the usual places, take off my build engineer’s cap, and go to sleep.