Selasa, 25 Januari 2011

2010-12-28 Trunk builds

Fixes:



  • Fixed: 572417 - OOPP: Full-screen flash videos don't have working video controls.

  • Fixed: 616397 - new Image() doesn't work in Greasemonkey scripts.

  • Fixed: 615723 - Turn on methodjit for DOM workers.

  • Fixed: 606678 - Use openLinkIn in nsContextMenu ('Open Link in New Tab' shouldn't add tabs to popups).

  • Fixed: 616271 - Plugin-like files add overhead on every startup.

  • Fixed: 573039 - [Linux] Segfault with CUPS 1.4.4 (Print and Print Preview do not work).

  • Fixed: 578877 - [Linux] Re-enable ANGLE and WebGL (?) on Linux.




All changes between 2010-12-20 nightly and 2010-12-28 nightly





Windows builds:

Win32 nightly,
Win64 nightly

(discussion)





Mac builds:

Mac nightly






Linux builds:

Linux32 nightly,
Linux64 nightly

2011-01-09 Trunk builds

Fixes:



  • Fixed: 605662 - Allow garbage collection per compartment.

  • Fixed: 570012 - Show download progress indicator when installing add-ons.

  • Fixed: 613909 - Disable pinch gestures by default & revert three finger vertical swipe gestures.

  • Fixed: 572160 - [Windows] Put tabs in the title bar when Firefox is maximized.

  • Fixed: 531552 - [Mac] Firefox opens two windows when opening external links.

  • Fixed: 617656 - Footprint: Discard jitcode to avoid excessive memory consumption.

  • Fixed: 577359 - Footprint: Don't generate INITPROP/INITELEM for constant initializer elements.

  • Fixed: 610070 - Footprint: Large amount of heap allocation from js::PropertyTable::init.

  • Fixed: 591972 - JM: Generate inline code for JSOP_TABLESWITCH.

  • Fixed: 610823 - nsTArray should default to infallible.

  • Fixed: 596481 - Geolocation sometimes hangs without returning result or running any callbacks.

  • Fixed: 363861 - GDI ClearType rendered to RGBA surfaces sometimes looks bad.

  • Fixed: 594889 - [Dwrite] wrong margins between characters in text and overlapping chars with no Cleartype.

  • Fixed: 590568 - [D3D9] plugin area is shown in toolbars when scrolled off the screen as a rectangle about the size of plugin area being scrolled.




Fixes for recent regressions:



  • Fixed: 622117 - Links with href broken if JavaScript is disabled and onclick attribute is present.




All changes between 2010-12-28 nightly and 2011-01-09 nightly





Windows builds:

Win32 nightly
(discussion)





Mac builds:

Mac nightly






Linux builds:

Linux32 nightly,
Linux64 nightly

2011-01-19 trunk builds

Fixes:



  • Fixed: 598921 - Reduce default addon bar height.

  • Fixed: 622482 - [Windows] Support subpixel-AA when drawing to transparent surfaces with DirectWrite.

  • Fixed: 569850 - [Windows] For tabs in the title bar, background tabs shouldn't be transparent under Win XP and Win 7/classic.

  • Fixed: 613696 - Minefield button randomly changes sizes.

  • Fixed: 609685 - FOUC and other excessive painting if Panorama has ever been opened in the window.

  • Fixed: 522375 - Built-in startup time measurement (extension to make it visible).

  • Fixed: 612025 - window in a user script is no longer a XPCNativeWrapper object for Greasemonkey.

  • Fixed: 624588 - Change Panorama shortcut to Ctrl+Shift+E (Shift-Cmd-E on Mac).

  • Fixed: 620472 - 'Work offline' shouldn't be managed by Firefox, only by the user.

  • Fixed: 573875 - for (var p in localStorage) is failtastic.




Fixes for recent regressions:



  • Fixed: 624265 - Undo most recently closed tab creates a new tab group and switches to it.



All changes between 2010-12-28 nightly and 2011-01-09 nightly





Nightly builds
(discussion)

Alexander Limi: Help us finish Firefox 4

(You are encouraged to read this article with its formatting and typography intact, instead of in this RSS reader)

We’re very close to releasing Firefox 4, and the team & contributors are doing amazing work these days to fix the final remaining bugs, and get the new version out the door.



The current plan is to ship two more betas — beta 10 & beta 11 — so we have until the end of the month — that’s 7 days as of this writing — until beta 11 freezes. More information in Christian Legnitto’s post about the release schedule.



If you’re an employee or contractor for Mozilla, your job is pretty clear:



Get the number of hard blockers down to zero.



In addition to the “hard blockers” — essentially, bugs we will delay the release for — there’s a category called “soft blockers.”
These are bugs and improvements that we wouldn’t hold the release for in isolation, but if we didn’t fix any of them, the product we’re shipping won’t of be the quality you expect from Firefox. So it’s an aggregate way of looking at it, and we’d like to fix as many of these as possible before release.



This is where you as a community member can make a difference. If you’re a community member — or have exhausted the hard blockers you are capable of helping with — your next step should be to look at the list of soft blockers, and help resolve these.



A large number of UI bugs naturally falls into the soft blocker end of the spectrum, since they are often a case of “this is unfortunate, but not a showstopper” — with some obvious exceptions. We know we can’t get them all fixed before the release, but that won’t stop us from trying!





How do you choose which soft blockers to pick up if you want to improve the user experience of Firefox 4, and have exhausted the hard blockers you can help with?
There are some bugs that we’d like to call out, that we think would make Firefox 4 a lot better:





  • Fix one of the very visible bugs in the main window — A large number of these bugs are tracked via the live updated, annotated screenshots on areweprettyyet.com1.

    1 The name started as a reference to its sister site, arewefastyet.com, which tracks Firefox JavaScript performance against other web browsers. Of course, we list things that are more about interactions and that are more than skin deep, but the name stuck, and “pretty” in this context means more than just pixel-level polish.

    Make sure you take a look at all the different areas listed under the “Project” menu, and also note that you can list all the bugs in a particular project in Bugzilla form by going to “Actions” → “View all bugs in a Bugzilla table.”



  • Help clean up the “traditional” menu (used on Windows XP, Mac OS X and some variants of Linux) — this is mostly simple fixes to move or remove menu items now that the necessary infrastructure support for this (bug 607224) has landed. See Alex Faaborg’s comprehensive overview of the changes that need to be done.


  • Help simplify the add-ons manager — the tracking bug for this is bug 623250, and Jennifer Boriss has also blogged about this. Several of these are a simple matter of just knowing enough about CSS to help out.


  • Update Start page with no string impact — bug 627301
  • Remaining work on the URL preview — bugs 625952, 625945, 625956.


  • Add-on bar missing shortcut — bug 616015
  • Animation when closing doorhangers, so it's obvious how to get them back — bug 610545 (requested soft blocker)


  • Styles for geolocation and password manager (bug 615471) + site identity (bug 610053)


  • Streamline search field, has patch that works on all platforms except XP right now, bug 592909
  • Search field isn't tab-specific when tabs are on top, which breaks the conceptual & visual hierarchy: bug 565740

  • Any other bug on the soft blocker list.




Firefox 4 is already an amazing release — you’re running the betas, right? — and this is your chance to help put it over the top by fixing one of the soft blockers. If you have any comments or need help getting started, you can find me on Twitter.

Mozilla Open Data Competition – Announcing The Winners!

[Note: cross-posted on the Blog of Metrics]


Back in November, Mozilla Labs and the Metrics Team together launched the first Mozilla Open Data Visualization Competition. While we set out to discover creative visual answers to the open question, “How do people use Firefox,” we really didn’t know what level of participation to expect from the Mozilla and data analysis communities. In fact, we were overwhelmed by both the number and quality of submissions – so much so that we had to give ourselves an extra few days to thoroughly review them all!


In all, we received 32 high-caliber submissions. The “visualizations’ took a number of forms, from tools to easily query the data to interactive web applications. They also covered a broad range of important topics, from plugin memory consumption to user web activities. You can find all 32 submissions here; entrants, if you haven’t already, be sure to check out the page as our panel of judges has left feedback on each and every submission.


Needless to say, we want to thank all the participants – your work has made our initial open data competition an overwhelming success and many of your insights will directly help the Firefox team develop a better web browser. In thanks, we’ll be sending this awesome Firefox t-shirt to each entrant:



We also want to thank our 3 partner judges: David Smith, Revolution Analytics; Andrew Vande Moere, Information Aesthetics; and Brian Suda, author of A Practical Guide to Designing with Data. The success of the competition was largely due to your help in publicizing the event and thoroughly evaluating the entries.


And now…lets get to the winners!


Grand Prize


Survey Participants vs. All Users – Contributed by: James Fiedler



While deciding amongst the 32 entries was difficult, the focus on a single, very relevant and important question distinguished this entry. James focused on contrasting survey participants with all users (critical as we often use survey data for segmentation), then set up a simple and helpful environment for the user to explore and discover interesting conclusions of their own. This submission is exactly the type of work we were hoping for: an elegant visualization that presents data around an important and complex question in a clear and easy-to-understand way. James will receive a $300 Amazon gift card for his excellent work.


Finalists


Test Pilot Explorer – Contributed by: Lon Riesberg



One of the more creative entries, Lon created a custom “explorer” that essentially “plays back” time-ordered events as animated plots and includes filters to customize what data is shown. This explorer really shows how you can “see” user behavior on a mass scale, and while we had some quibbles about some of the details of the visualization itself, we found it to be a powerful and enjoyable data exploration tool. Lon will receive a set of all 4 Edward Tufte books for his work.


Firefox Usage by Age – Contributed by: Tom Haynes (University of Michigan)



Tom’s entry also focused on one particular element of the data. His execution sets this submission apart, as his visualization doesn’t try to encompass everything, but tells a clear, specific story around how Firefox usage times vary across age groups. Tom will receive a set of all 4 Edward Tufte books for his work.


Honorable Mention


Given the number of worthy submissions, we decided to hand out 5 Honorable Mention Awards in addition to the original 3 prizes. For varying reasons, we thought these entries were particularly valuable and each team will receive Tufte’s latest book, Beautiful Evidence, in recognition of their great work. Good Job!


Firefox browser – Event Sequences – Contributed by: BenoĆ®t Pointet


Firefox 4 beta UI Component Use vs. User Expertise – Contributed by: Nicolas Garcia Belmonte, Maria Luz Caballero


Browser Usage Over the Course of a Day Contributed by: Christian Kreibich


Bookmark a Lot, Browse a Lot – Contributed by: Eugene Tjoa


Firefox Plugin Memory Consumption- Contributed by: Diederik van Liere and David Eaves


Again, thanks to all the participants, judges, and everyone else who helped make this first open data competition such a success! Participants should receive an email within the week with details on how to receive the prizes and t-shirts.

Miramar (Thunderbird 3.3) Alpha 2 now available for testing

Miramar Alpha 2, available here for download, is for testers, extension developers, and friends who are curious to follow the development of our next release of Thunderbird.


Miramar Alpha 2 is built on top of Gecko 2.0 and includes a new Troubleshooting information page, improvements to add-on notifications and attachment handling, and numerous other bug fixes. We expect to release further interim releases as we work towards the next major version of Thunderbird.


Please read the release notes for more details.

the web is not built on patents

No one owns the Web. It's not built on patents. People building Web sites and applications, people using Web sites and applications, and people building Web browsers and other Web clients all benefit from this very important freedom whether or not everyone realizes it.



Mozilla, and our friends over at Opera, have insisted on this important fundamental principle of the Web as we've built out support for HTML5 <video> in our browsers. Today, with notice that they intend to stop shipping the patent encumbered h.264 video codec in Chrome, Google has joined Mozilla and Opera and lent its significant weight to this critical aspect of the Web.



With approximately 40% of Web usage happening through these three browsers, VP8+Vorbis in WebM will soon have the critical mass it needs to become the standard video technology for HTML5's <video> tag.



update: Mozilla's Mike Shaver has a great post on this development.