Looks like this has made its way to the Ajaxian:
http://ajaxian.com/archives/prototype-2-0-will-not-extend-the-dom .
Interestingly, some commenters suggest that *not* extending the DOM will
result in a faster framework, which I have to say feels somewhat
counterintuitive; as Aaron points out, surely that would just slow
non-IE browsers down, rather than speed up the framework generally.
I'd be interested in some sort of "halfway" extension of elements in IE
-- that is to say, using document.id() gets you some baseline
functionality across all browsers (eg set(), get(), inject(), adopt(),
etc), whilst document.uberID() gets you all of the functionality
available. I find that there are a few extensions (such as inject())
that I use an awful lot, whilst others I use only rarely. What do you
think? Is this a feasible "half-way" solution to the problem?
On 07/04/10 04:14, Fábio M. Costa wrote:
Mootools 1.3 will have a new selector engine (Slick) that provides a
public API for selecting nodes, so it will be easy to select nodes
without the need to extend them, as you need.
--
Fábio Miranda Costa
Solucione Sistemas
Engenheiro de interfaces
On Tue, Apr 6, 2010 at 4:43 PM, Aaron Newton <[email protected]
<mailto:[email protected]>> wrote:
If we implement wrappers, it won't speed things up for IE, it'll
slow down everything for the other browsers (that allow us to
alter the Element prototype as we do currently).
Obviously we shouldn't have to "work around" the JavaScript
framework
integrated, it should provide ease of use in every situation.
That is always our goal.
--
Not sent from my Apple ?Phone.
--
To unsubscribe, reply using "remove me" as the subject.
