Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News What Do You Want On Future Browsers? Time to Vote!

What Do You Want On Future Browsers? Time to Vote!

This item in japanese


An industry wishlist for future browsers has been collected and developed by OpenAjax Alliance. Using wiki as an open collaboration tool and with contributions from many people in the industry, the feature list now lists 37 separate feature requests, covering a wide range of technology areas, such as security, Comet, multimedia, CSS, interactivity, and performance. The goal is to inform the browser vendors about what the Ajax developer community feels are most important for the next round of browsers (i.e., FF4, IE9, Safari4, and Opera10) and to provide supplemental details relative to the feature requests.

The current feature request list is:

Security features

Client-server communications features

HTML5/W3C features

CSS features

Rendering/interaction/event handling features

Performance features

JavaScript features

Other features

OpenAjax Alliance is calling for everyone to vote for his/her favorite features. As befits an AJAX organization, voting is done using AJAX callbacks so that the votes are recorded asynchronously in the background:

  1. Register an account for yourself at OpenAjax wiki home page;
  2. Cast your vote at Phase II Voting Page;

The alliance also strongly encourages people to comment on the wiki pages for each of the existing features and to add any important new features that are not yet on the list.

This voting is open to anyone, including OpenAjax Alliance members and non-members.

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Resolve the Political issues first , later technical !

    by siva prasanna kumar P,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I may sound like a Rebel but the fact is these words are coming from experience of facing useless Browser specific ways of doing things (better say fixing issues).

    If you take a count of the number of people trying to fix the same x/html code with some java script and dhtml to behave same on all the major browser, you will get almost 100% of all the web developers in this count.

    In fact more than any thing addressing this issue must be given highest priority, Enough of customizing the same code for various browsers, first of all this should never be a developers or testers concern, I have seen my own friends installing 3-4 browsers to check if the behavior of the same page is same on all the browsers on not! Some times that effort is more expensive then development it self!!

  • Things I like

    by Deepal Jayasinghe,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    In my view there are few items which might be very useful.
    - Support for native JSON parsing mechanism , seems to be a good thing. First thing is JSON is very popular so having parser will enable easy integration.
    - Offline support is also a cool feature , because that will help Ajax developer a lot
    - Xpath support

  • Page change notification

    by Sandeep Khurana,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Not sure if this functionality already exists or not but can there be way to notify the user as and when a web page is updated? Example is a tutorial on a technical topic, when a new version of the framework/product is released and the tutorial is updated I would like to be notified.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p