Feature Requests Summary Page

From RuntimeWiki

Jump to: navigation, search

This wiki page holds the list of feature requests that are under discussion.

The first section lists the feature requests that are under active discussion. At the bottom, there is a second section that lists various feature requests that are now inactive, along with reasons why they are inactive.

We are now in Phase I (see Timeline at the bottom of Main Page), where participants not only add comments, but also are asked to identify their Top 5 features (i.e., those features that are most critical for inclusion in next-generation browsers). To cast your 5 (or so) votes, simply go to the Phase I Voting wiki page, edit that page, and add a section which shows your name and your votes.

In addition to voting, please help us perfect the list and the write-ups for the various features. It is OK to add new features to the list if you see something important that is missing. Anyone is welcome to participate. To gain write access, see the instructions at Main Page

Active Feature Requests

The following table contains a row for each of the feature requests that are under active discussion. The first column contains a short title for the given feature. The second column will be filled out during a later phase and ultimately will provide an executive summary about how the various contributors to this wiki felt about the importance of this feature, such as whether it was considered a top priority by many contributors, considered a low priority by many contributors, or there was a significant difference of opinion about the priority. The third column provides the link to the wiki page that provides details about the given feature. The details include description, why is it important, possible solutions, references, discussions and voting.

FeaturePriorityWiki page
Security features
Better Security for Cross-site Scripts(coming later)Better Security for Cross-site Scripts
Stronger Cross-site Request Forgery Protection(coming later)Stronger Cross-site Request Forgery Protection
Better IFrames Better Sandboxing(coming later)Better IFrames Better Sandboxing
Native JSON Parsing(coming later)Native JSON Parsing
Client-server communications features
"The Two HTTP Connection Limit" Issue(coming later)The Two HTTP Connection Limit Issue
"Persistent Connections" Issue(coming later)Persistent Connections Issue
XHR Connection Length Advice(coming later)XHR Connection Length Advice
HTML5/W3C features
2D Drawing/Vector Graphics(coming later)2D Drawing/Vector Graphics
Video and Audio(coming later)Video and Audio
Offline Support(coming later)Offline Support
Mutation Events(coming later)Mutation Events
XPath Support(coming later)XPath Support
Component Model XBL HTC(coming later)Component Model XBL HTC
CSS features
Gradient Fill(coming later)Gradient Fill
Blur Effect(coming later)Blur Effect
Rendering/interaction/event handling features
Better Support for Rich Text Editing(coming later)Rich Text Editing
Better APIs about positioning and styling(coming later)Better APIs Positioning Styling
Better UI Layout Support(coming later)Better UI Layout
IE 6 and IE 7: "overflow: auto" problem(coming later)IE's overflow:auto problem
Event Transparency API(coming later)Event Transparency API
Event notification for "content overflow"(coming later)onOverflow Event
Drag Drop Copy Paste(coming later)Drag Drop Copy Paste
Override Back Button Event(coming later)Override Back Button Event
Performance features
"Array" Operation Performance In All Browsers(coming later)"Array" Operation Performance
HTML DOM Operation Performance In General(coming later)DOM Performance
Matching Element Against CSS Selector(coming later)Matching Element Against CSS Selector
JavaScript features
IE: Array’s Can’t Be Usefully Sub-classed(coming later)IE "Array" Sub-classing
JavaScript Coroutine Support (was Pause Release)(coming later)JavaScript Pause Release
Threading Support(coming later)Threading Support
Other features
Hashes for DOM elements and associated API(coming later)Client_Element_Hash
Ajax toolkit caching(coming later)Ajax Toolkit Caching
Animation of web page content(coming later)Animating Web Page Content
Better testing support(coming later)Better Testing Support
CSS Object Model(coming later)CSS Object Model


Inactive Feature Requests

The following table contains various feature requests that we have decided to declare as inactive. The "Reason" column explains why the feature is inactive.

Note: If you disagree with the placement of a given feature within the inactive table, please speak up, such as adding notes to this wiki (requires a wiki login), send email to runtime@openajax.org (only open to OpenAjax members), send email to public@openajax.org (open to the public, but you must subscribe first), or send email to Coach Wei (coach-at-nexaweb.com) or Jon Ferraiolo (jferrai-at-us.ibm.com).

FeatureWiki pageReason for being classified "inactive"
Improved Client Side Persistent Storage and Caching Client Side Storage and Caching Latest browsers already are addressing this by implementing HTML5 client-side storage
Cross Frame Communications Support Cross Frame Communications Support Latest browsers already are addressing this by implementing HTML5 postMessage
Cross-domain Secure Data Access Cross-domain Secure Data Access Latest browsers already are addressing this by implementing either W3C/Access Control or MS's XDomainRequest
Performance - JavaScript, JIT JavaScript Engine Implementation Performance Already getting addressed. Some of the more recent browsers have faster JavaScript engines, showing that the browser teams probably already "get it", so let's hammer on other things. Anyways, various people have said it's probably more important to speed up DOM calls.
“String” Manipulation Performance on IE “String” Performance on IE At the F2F meeting, we were told IE8 has addressed this performance issue.
Performance of “eval”, Object Creation and “in” Operations on FireFox FireFox Specific Performance Issues At the F2F meeting, we were told FF3 has addressed this performance issue.
Bleed-through problem of overlapping elements bleed through problem At the F2F meeting, we were told that this is fixed in FF3 and IE7, therefore "already getting addressed".
Z-Index Context Z Index Context Already getting addressed. This simply is a bug in existing shipping versions of IE.
Scoped IDs Client Scoped ID At the OpenAjax F2F on 2008-03-21, there was a consensus that the underlying requirement would be better solved in a different way. See Client Scoped ID for details.
Mashup Security Mashup security Two reasons for moving this to inactive: (1) The various requests around IFrame improvements overlap this one, (2) One of the specific requests contained within this feature, postMessage(), is already being addressed by the various browsers.
Features relevant to OpenAjax artifacts AJAX Features Originally was a placeholder feature, but no one ever provided any details, so inactive until someone adds substance to this item
Calculating Computed Box Model and Style Computed Box Model and Style Made inactive because it was pretty much redundant with Better APIs Positioning Styling. Now, all of the key content from this feature has been merged into Better APIs Positioning Styling.
Personal tools