56
edits
(→Tests) |
(changed headings to <h2>) |
||
| Line 9: | Line 9: | ||
}}<section end="summary" /> | }}<section end="summary" /> | ||
= Vision = | ==Vision== | ||
This roadmap covers the surface area that we will expose to web developers in order to let them build the next generation of web applications. Overall our vision for Firefox's role in the web ecosystem is: | This roadmap covers the surface area that we will expose to web developers in order to let them build the next generation of web applications. Overall our vision for Firefox's role in the web ecosystem is: | ||
| Line 17: | Line 16: | ||
This roadmap covers the high-priority items that we should accomplish during 2012 in order to achieve this goal. We've broken the list of items roughly down by domain area, with small amounts of context around each one. | This roadmap covers the high-priority items that we should accomplish during 2012 in order to achieve this goal. We've broken the list of items roughly down by domain area, with small amounts of context around each one. | ||
= Networking = | ==Networking== | ||
Networking covers several areas that are important to improving experiences in web browsers. In particular, there's a decent amount of work that can be done to improve performance. During 2012, we would like to be able to deploy SPDY, which offers significant performance improvements to end users on sites with many resources, as well as better resource management for servers. | Networking covers several areas that are important to improving experiences in web browsers. In particular, there's a decent amount of work that can be done to improve performance. During 2012, we would like to be able to deploy SPDY, which offers significant performance improvements to end users on sites with many resources, as well as better resource management for servers. | ||
| Line 63: | Line 61: | ||
|} | |} | ||
= Apps = | ==Apps== | ||
There are a lot of tasks around Apps that need doing. These fall into a few major categories: | There are a lot of tasks around Apps that need doing. These fall into a few major categories: | ||
| Line 155: | Line 152: | ||
|} | |} | ||
= Devices = | ==Devices== | ||
While it's important to build a developer ecosystem to enable payments and a great install experience it's also important that we enable a set of web APIs for access to devices connected to a computer, tablet or phone. This includes everything from access to an NFC device, to offline storage to raw touch events from your tablet. | While it's important to build a developer ecosystem to enable payments and a great install experience it's also important that we enable a set of web APIs for access to devices connected to a computer, tablet or phone. This includes everything from access to an NFC device, to offline storage to raw touch events from your tablet. | ||
| Line 214: | Line 210: | ||
Proximity to Your Face (B2G) - Q2 | Proximity to Your Face (B2G) - Q2 | ||
= Layout = | ==Layout== | ||
In the area of layout we need to enable a bunch of new ways to express layouts that designers have used through other tools for years. These include flexbox, which is very similar what what we've been using to layout the Firefox UI for years, Grid and Regions & Exclusions. All of these enable new kinds of experiences. | In the area of layout we need to enable a bunch of new ways to express layouts that designers have used through other tools for years. These include flexbox, which is very similar what what we've been using to layout the Firefox UI for years, Grid and Regions & Exclusions. All of these enable new kinds of experiences. | ||
| Line 277: | Line 272: | ||
|} | |} | ||
= Media = | ==Media== | ||
Media presents one of the most interesting areas where there's opportunity to build something amazing. These fall into a few areas of note: | Media presents one of the most interesting areas where there's opportunity to build something amazing. These fall into a few areas of note: | ||
| Line 325: | Line 319: | ||
|} | |} | ||
= Tests = | ==Tests== | ||
We started to ship parts of HTML5 in Firefox 3.5 The spec has moved since then, and there are still some small parts we need to finish. These are often tested on sites as a kind of proxy for standards support and we should invest in finishing where it's appropriate. | We started to ship parts of HTML5 in Firefox 3.5 The spec has moved since then, and there are still some small parts we need to finish. These are often tested on sites as a kind of proxy for standards support and we should invest in finishing where it's appropriate. | ||
edits