New in Firefox Nightly: In-content Preferences
18 May, 2014 § 46 Comments
I’m happy to announce that starting today, the new in-content preferences are enabled by default in Firefox Nightly.
This project was started by a group of students at Michigan State University and was mentored by Blair McBride and myself. Since its start, it has continued to get a ton of attention from contributors world-wide.
This is a list of people who have contributed patches to the in-content preferences as of this posting:
- Ally Naaktgeboren
- Andres Hernandez
- Andrew Hurle
- Benjamin Peterson
- Benjamin Smedberg
- Brendan Dahl
- Brian R. Bondy
- Brian Smith
- Carsten “Tomcat” Book
- Chris Mahoney
- Chris Peterson
- Christian Ascheberg
- Christian Sonne
- Devan Sayles
- Dão Gottwald
- Ed Morley
- Ehsan Akhgari
- Florian Quèze
- Gervase Markham
- Gijs Kruitbosch
- Gregory Szorc
- Honza Bambas
- Jan de Mooij
- Jan Varga
- Jared Wein
- Javi Rueda
- Jeff Walden
- John Schoenick
- Jon Rietveld
- Jonathan Mayer
- Josh Matthews
- JosiahOne
- Kyle Machulis
- Mahdi Dibaiee
- Manish Goregaokar
- Manish Goregaokar
- Mark Hammond
- Martin Stransky
- Matthew Noorenberghe
- Michael Harrison
- Mike Connor
- Mike Hommey
- Ms2ger
- Nicholas Nethercote
- Nick Alexander
- Owen Carpenter
- Paolo Amadini
- Phil Ringnalda
- Richard Marti
- Richard Newman
- rsx11m
- Ryan VanderMeulen
- Sebastian Hengst
- Sid Stamm
- Ted Mielczarek
- Theo Chevalier
- Tim Taubert
- Yosy
- Zuhao (Joe) Chen
There is still a lot of work to be done before shipping the new in-content preferences out to people on the release builds of Firefox. That also means that this long list of contributors doesn’t have to stay at 59 people, it can keep growing 🙂
We have a list of bugs that we need to fix before we can call version 1 of this project complete. The easiest way for someone new to help out is to download Firefox Nightly and help test that the new preferences work just as well as the old preferences. If you find an issue and see that it hasn’t already been reported, please file a new bug in Bugzilla and leave a comment on this blog post with a link to the bug that you filed.
JAWS
Is the use of non-native widgets intended for the final product? I believe this would be a terrible idea. Widgets should be native (or conform as much as possible to the native OS) for reasons of usability, familiarity, consistency, correct theming, accessibility, performance, stability, etc. Google Chrome recently ditched native widgets, causing all kinds of bugs/misbehaviors and making everything look, act, and feel wrong. Please respect the OS platform in Firefox, and hopefully save some developer time in the process.
[…] *1 : https://bugzilla.mozilla.org/show_bug.cgi?id=738797 *2 : https://msujaws.wordpress.com/2014/05/18/in-content-preferences/ […]
It’s nice, but wish there was some other way, like in a panel instead of a tab or modal window. Only because it’s Google Chromeish
Being different for the sake of being different doesn’t help Firefox when our goals are to bring the best experience to the people that love using the browser. Some things Chrome does well, and there are some things that Firefox does well that other browsers have adopted as well.
This might have been mentioned before, but the look and feel for this is completely different from the add-ons page. Is this intentional or are there plans to change the add-ons settings page to get this new look as well?