Resources: sayrer
== Colour Management Tests ==
Write [http://developer.mozilla.org/en/docs/Creating_reftest-based_unit_tests reftests] to compare images in order to deal with floating point tolerance. This includes dealing with things like Monitor Profiles, profiles in JPEG (i.e., JPEGs get changed based on colour profile info). See discussion of colour profiles in Firefox 3 [http://www.dria.org/wordpress/archives/2008/04/29/633/ here]. It would be useful to be able to compare to PNGs with a reftest, perhaps creating an image diff tool, where pixels outside a floating point tolerance (> 0.n) would somehow be highlighted so you can see what is different. <strike>Little CMS (lcms) needs test coverage too.</strike> Done.
This will require some graphics and image knowledge (i.e., Photoshop, what colour is on a computer, etc).
Resources: #gfx, joe, vlad, bholley, [http://bholley.wordpress.com/2008/09/12/so-many-colors/ discussion of Mozilla colour profiles]
== Plugin Code Test Suite ==
Resources: jst
== Per-Site/Per-Tab User-Agent Modification ==
Create an extension that lets a web developer modify the User-Agent string on a persistent per-site, per-tab basis. There's already a user-agent-switcher in the FF-addons (https://addons.mozilla.org/en-US/firefox/addon/59) but it doesn't isolate the user agent per site or per tab. Strong features might include a separation of the browser identification and language support, optional persistence across browsing sessions and a UI that by default hides the UA string behind the name/version of the browser it represents. See [http://www.webaim.org/blog/user-agent-string-history/ this] discussion of the UA's history.
Resources: mhoye
== Add Source Server Support for Mercurial ==
