Various input documents to the Ajax runtime issue list draft
From MemberWiki
This page contains the various inputs to the Ajax Runtime Issue List Working Draft document.
Inputs
- Jon Ferraiolo thoughts on this task force: Jon Ferraiolo Thoughts 20071001
- Past content copied from Best Practices Browsers
- Suggestion for cross-domain XMLHTTP access by Haik Sahakian, also on Jon Ferraiolo Thoughts 20071001
- Two HTTP connections per frame
- Attention to browser memory leaks
- Future releases of browsers SHOULD NOT include changes which break existing Ajax content that conforms to commonly accepted industry practice and/or OpenAjax Best Practices.
-
From Bertrand Le Roy (Microsoft)
- Xpath that works on documents created on the fly from strings as well as from documents fetched over the network and the HTML DOM.
- An API that gives reliable absolute pixel coordinates of an arbitrary element relative to the top-left corner of the document. IE's getBoundingClientRect is a good start but has a few quirks such as its two pixel offset for all parent frame borders.
- CSS selection APIs.
- A reliable loaded event on script tags (this will be apparently done once Safari 3 is out).
- Committing to the Firefox and Opera behavior for fragment navigation (a history point gets created and hitting back restores the url including the fragment).
- An API to access, manipulate and get events from the browser's history without having to resort to frgment hacks and pooling. A way to handle refresh would help too.
- Accessibility.
- JIT for Javascript.
- Behaviors/XBL bindings.
- Name/id scopes in the DOM to facilitate templating scenarios.
- Alex Russell: [The Browser.Next List]
- Ajaxian (I don't have the source):
- 2D drawing and support for canvas
- JIT for Javascript
- Better memory management for Javascript
- Offline storage API
- Nikhil Kothari: [Browser/Scripting Wish List]
