The Ajax community ranks vector graphics as top request
OpenAjax Alliance has produced a summary report of its browser wishlist initiative at:
By July 13, when the voting closed, this initiative has turned out to be a bigger success than expected. Given the amount of effort required to read and understand the vast web technology landscape, and the relatively limited time and resources available to the OpenAjax Alliance Runtime participants, we were hoping for 50 or so people to vote, which would be meaningful to establish a rough idea of what’s most important to the community.
Voting results are available at:
Here are some quick statistics:
- 222 people participants
- 143 people voted
- 55 feature request being written up
- Various industry leaders contributed
- A discussion thread spawns on Slashdot with 628 comments (http://tech.slashdot.org/article.pl? sid=08/06/30/1845201)
Among all the feature requests, 2D Drawing/Vector Graphics is clearly the most desired feature by the community. It received most votes (110 people voted for it), and highest total score (842, over 10% higher than the second feature request). The second top feature request is enhanced security for cross-site scripts. The third and fourth were better APIs for scripting and styling and HTML DOM performance. Here are the top 10 features:
- 2D Drawing/Vector Graphics
- Better Security for Cross-site Scripts
- Better APIs about positioning and styling
- HTML DOM Operation Performance In General
- Better Support for Rich Text Editing
- The Two HTTP Connection Limit Issue
- Better UI Layout Support
- Native JSON Parsing
- Persistent Connections Issue
- Video and Audio
Here is what pops out from the voting:
- Better low-level CSS and DOM support for layout – Two of the top vote-getters were Better APIs for positioning and styling and Better UI Layout Support. These requests come from the widget developers within Ajax toolkit projects who design Ajax-based UI controls by taking advantage of what the browser gives them, such as DOM, CSS, images, and table layout. They often run into walls, and their jobs could be much easier (and performance much faster) if the browser included a small number of additional (relatively small) features, such as stretchable layout (e.g., flexbox in XUL) and the ability to determine the location and size of objects (and containers) within the page.
- Rich text editing – Various people in the Ajax community want to move desktop-like document editing into the browser. However, the contributors to this feature request did not outline a detailed strategy for how to accomplish this in future browser. The takeaway is that the Ajax community wants Better Support for Rich Text Editing , and hopefully one of the browser teams will push the envelope in this direction and send standards proposals so that the other browsers can also provide this functionality.
- Comet (server push) – Two of the top vote-getters were The Two HTTP Connection Limit Issue and Persistent Connections Issue. The underlying requirement is that many Ajax applications, such as dashboards, require an efficient and robust mechanism for having the server send data to the client on an event-driven basis. Today, server push in Ajax is often accomplished using â€œCometâ€ techniques such as long-lived HTTP connections, but the Ajax community would prefer if server push was a native browser feature.
- Video and Audio – Video and Audio also receiving strong support, coming in as the 10th-most requested feature.
The next step is to communicate with browser vendors. We have had calls with some of the browser vendors such as Microsoft IE team during Phase I. OpenAjax Alliance will try to get in touch (or continue) the dialog with browser vendors to convey what the community is looking for.ser vendors to convey what the community is looking for.