When importing from IE, Firefox could look at what buttons the user has enabled in IE and enable all the buttons that have Firefox equivalents. Firefox could even import the order of the buttons. I don't know if this is a good idea. For one thing, the toolbar could get cluttered if we imported toolbar buttons from IE and also showed the search bar by default. From http://slashdot.org/comments.pl?sid=114042&pid=9660612: "I finally convinced my mom to switch a few weeks ago.... she asked why there was no history button on the toolbar."

I'll investigate.

Trimming the 1.0PR list since this doesn't seem to have localization impact. Bring in if you fix or trim your PR+ set ahead of time.

For now, this is off the 1.0 radar. However, if some Windows-savvy person could look into this and provide all the information we need to do the migration, it might get back on the radar.

Button types, text and icons options.

Based on previous discussions we had while working on Migration rewrite, Firefox offers a quite different UI experience from IE, and in some cases we believe it's a better experience. Importing the toolbar settings from a different browser may partially break this experience that is what makes Firefox unique and appreciated. Let's just think to the attached refresh button, disappearing forward button, the urlbar/searchbar resizing behavior, social, and in future more entries that may have some special behavior. Importing an exotic config may "break" some of these, we can't predict positioning. Australis will also be a complete different experience for UI customization that can hardly cohexist from this kind of import. For these reasons I'm going to call this a wontfix.