Just for fun, I decided to whip up one big awesome demonstration of some new CSS3 features in Firefox 3.1. @font-face { font-family: Delicious; src: url('http://blog.mozilla.com/webdev/files/2009/02/delicious-roman.otf'); } #css3test { width: 350px; margin:... »
Ah, inline-block, that elusive and oh so tempting display declaration that promises so much, yet delivers so little. Too many times have I received PSD files like this: and begin to cry. Normally, this type of layout would be a cakewalk. Fixed width, fixed height, float:left and you’re done. Buuuuut, the design needs to work with... »
In case you haven’t heard, one of Firefox 3.1’s awesome new features will be native JSON support. This is totally sweet for two reasons: eval’ing JSON in the browser is unsafe. Using native JSON parsing protects you against possible code execution. Safely eval’ing JSON with a 3rd party library can be orders of magnitude slower. Native... »
Over the past few months the Graph Server team and I have been hard at work re-writing the back end for the Graph Server and it’s finally come to fruition. For those that don’t know, the Graph Server is used to display performance test data of Firefox builds reported by Talos. Our work initially started... »
Recently I fixed bug 439269 (”AMO theme has unnecessary scrollbar at the bottom”) and thought it was an interesting bug for a few reasons. To summarize the issue, for no apparent reason in right-to-left languages a really long scrollbar would appear at the bottom of the window. Even though there was a scrollbar, when you scrolled... »
This Thursday and Friday we attempted to push updates to re-partition our crash report database and optimize the reporting tool to take advantage of it. This was the deployment of bug 432450 and a fix for bug 444749, among others. Our first attempt suffered from a network timeout, which required an eleven hour restore and... »
How big can a table in a database get? Well, the answer varies by database, for most modern databases, the answer is “really huge”. That’s what we’ve going in Socorro, some honking big tables. Queries can get slow on big tables. Sure you can add indexing to prevent having to... »
The Mozilla Tree (Be sure to check out the large version.) For the punchline first, go check out what just went live at feeds.mozilla.com. The rest of this entry is the back-story. You see, behind Firefox is Mozilla, and behind Mozilla is a community. And the Mozilla community acts a lot like an ecosystem, which can... »
Working with ss and chofman, we’ve created 2 new types of reports: a Top Crashers by Url and a Mean Time Before Failure (MTBF). Given the current state of performance of the non-report parts of Socorro’s webapp, most of the thought and time have gone into the backend piece of these reports. You can read about the ReportDatabaseDesign on the project’s... »
As part of our ongoing work on the Mozilla crash reporting system (codenamed “Socorro”) a redesign of the entire interface is in the works, and I have some preliminary wireframes to share for feedback and discussion. My personal goals with this redesign are to make working with crash data more efficient, and to make each... »
Three weeks ago today, we deployed the new Socorro file system into production. It was the first in in a series of engineered improvements to the Socorro codebase. By “engineered”, I mean that it was the first major improvement to the code that wasn’t done during an emergency with a gun to... »
There has been a lot going on for the Mozilla crash reporting system. Here are some quick links for project activity: Closed bugs Active bugs Code check-in RSS Socorro documentation Upcoming changes: Socorro site redesign – Neil and Austin are working with Sam and Chris to work through crash analysis to understand how the system is used to track... »
