This article is a stub. You can help MozillaWiki by .
This is an in progress page for documenting the overall priorities for standards work at Mozilla.
For an overview of technologies, see Standards/technologies.
Most of the web standards we implement are developed (or co-developed) at W3C, we must spend some time improving W3C architectural approaches and processes as a multiplier for both better standards focus and speeding up the development of specific standards:
This is a rough draft based on typical order of what developers build on when creating web pages, sites, apps, almost completely focused on client-side standards:
For the longer term health of the open web we must empower and liberate the server-side as well. That often requires working with different communities and specifications:
Lastly, we should proactively spend some time on experimental efforts that show potential:
HTML5 is fairly stable at this point and thus the spec priorities are accordingly:
- Fix features based on implementation experience
- Drop features that don't make sense or have not shown any practical need in building web apps.
- Reject feature proposals that lack clearly demonstrated needs in real world websites
CSS3 is a set of modules in various states from stable to experimental.
- Wrap-up specs we're editing that are nearly done
- Determine presentational blockers for web app UI and figure out which spec (or a new one) to get them into
We do this by working with the W3C CSSWG.
WebAPI is the focus for the overall JS/DOM area as that's where the key needs and work are currently.
(need finer grain list of priorities, defer to main WebAPI page for now)
Longer term priorities that are essential for the open web, and yet are not part of any direct specific web app needs. These efforts typically have a more server-side focus:
New concepts, or experimental / small community explorations