* August 23-25 W3C CSS WG f2f in Oslo http://www.w3.org/Style/Group/2010/Oslo
* September 3 dConstruct in Brighton http://2010.dConstruct.org/
== Ideas to Explore ==
Some ideas to consider exploring. These aren't tasks I'm taking on (yet) but rather a place to collect potential tasks. Feel free to grab any of these and ask me questions about suggested approach(es) etc. [[User:Tantek|Tantek]]
=== HTML5 support and documentation ===
A few ideas for improving the understanding and adoption of Firefox's HTML5 support. Help is definitely encouraged on any / all of these. Want to help out? Feel free to edit this section, add suggestions with your name (please sign with <nowiki>~~~~</nowiki> ), and volunteer to help out.
The better we document and explain Firefox's HTML5 support, the more developers learn about it and put it to use in real world web apps, the more feedback we get on Firefox's HTML5 implementation and know what to improve and iterate on, etc. A key goal here is to encourage an ever stronger feedback loop that improves the state of the art of HTML5 Web App development in general, and in particular with building increasingly higher fidelity HTML5+CSS3 Web Apps with Firefox as a development platform.
Some specific tasks that would help:
* Increased documentation of Firefox's HTML5 support/efforts in general (per release). Each release (even dotrevs) should come with a link to a support chart (for HTML5, CSS3 at a minimum).
** expanding/updating https://developer.mozilla.org/en/HTML/HTML5
* Public test cases that illustrate Firefox's HTML5 support
* Public support charts/tables summarizing Firefox's HTML5 support (linking to aforementioned test cases)
* A proper draft test suite constructed from those test cases (submit to W3C HTML WG)
* Implementation reports based on those test suites
* Perhaps a place to gather testimonials about Firefox's HTML5 support
See also: Top level [[HTML5]] page on this wiki.
=== additional potential CSS work ===
* '''pointer events''' (way of specifying whether an element is opaque to pointer events (and receives them) or is transparent to them (letting them get handled by what's underneath).
=== various UI thoughts ===
* "about:downloads" to address/bring up a "downloads window" view which would be one way to put the downloads window into a tab (and perhaps even enable that as a default option, downloads in a tab rather than separate window). This seems so obvious that there must be an existing bug / feature request for this.
== Reference ==
