Automagical stopObserving on update/remove? Event delegation modification in core (so you can attach delegated events to observe instead of having to write the same document.observe pattern with a series of if-s and element.match(cssSelector)?
Gareth On Thu, Jul 3, 2008 at 9:51 AM, kangax <[EMAIL PROTECTED]> wrote: > > +1 for hasProperties/isEmpty > I would also want to see #setProperty. > > Ken, which #escapeHTML fix are you talking about? We actually made few > changes in a current trunk. > > Besides what was mentioned: > > - deprecate Try.these > - deprecate Array#reduce (for compatibility with FF3+) > - update String#isJSON > > -- kangax > > > On Jul 2, 4:34 pm, Ken Snyder <[EMAIL PROTECTED]> wrote: > > Is avoiding document.write() for IE dom:loaded included in 1.6.1? I > > think the core team concluded that doScroll was the way to go, but I'm > > not sure. > > > > What about fixing String#escapeHTML for IE and WebKit? > > > > What about enhancing Element#siblings to accept a selector? > > (http://groups.google.com/group/rubyonrails-spinoffs/browse_thread/thr.. > .) > > > > What are the thoughts on adding an Object.isEmpty or > > Object.hasProperties? (http://dev.rubyonrails.org/ticket/10356) > > > > Thanks, > > > > - Ken > > > > John-David Dalton wrote: > > > I haven't seen the official roadmap for 1.6.1. > > > So here is my take on it. > > > > > 1.6.0.3 was a bug fix release. > > > I see 1.6.1 as an optimization and new feature/API release. > > > > > I see things like: > > > > > * Use of documentFragment (Huge IE boost in spots), > > > * Use of "_each" instead of "each" in places were we can > > > * Remove the event onunload mechanism for IE (I have a working > > > prototype of it) > > > * Avoiding wrapped methods internally (Element.method(element) > > > instead of element.method()) > > > * Implement "hasOwnProperty" for Safari 2.0.4 (can finally use it in > > > the rest of the code) > > > * Make $H(...).include() work properly > > > * Pass optional conditionals to methods like Element#show, > > > Element#hide and others) > > > * Optimize the Template class. > > > * Make Element#getStyle automatically convert units to px and handle > > > the "inherit" style. > > > * Use of Dimensions class > > > * Create various methods where needed: > > > - Object.isNodeList() > > > - Element#isOrphaned > > > - Element#getNumericStyle [cssToNumber] > > > > > * Ajax Fixes: > > > - Network error fixes > > > - Timeout added > > > - Abort added > > > - Detect when status 0 is allows (when its ftp or file > > > protocols) > > > > > I am sure I missed a few, but the good news is almost all of these > > > listed features/modifications have already been programmed. We should > > > be able to create the tickets and unit tests rather fast. > > > > > Do yall have anything else to add? > > > Here is a list of tickets currently marked to be addressed for 1.6.1 > > > (not nessesarily included in 1.6.1) > > >http://prototype.lighthouseapp.com/projects/8886-prototype/tickets?fi. > .. > > > > > - JDD > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
