On Tue, Nov 22, 2011 at 4:12 PM, Jonas Sicking <jonas@sicking.cc> wrote: > On Tue, Nov 22, 2011 at 10:24 AM, Ojan Vafai <ojan@chromium.org> wrote: > > On Tue, Nov 22, 2011 at 10:04 AM, Boris Zbarsky <bzbarsky@mit.edu> > wrote: > >> On 11/22/11 12:57 PM, Ojan Vafai wrote: > >>> I was hoping that we could have a fixed small list of properties > >>> that the spec says are exposed. Maybe that's too ambitious and doesn't > >>> actually buy us much though. > >> > >> Given the expando situation, I'm not sure that approach works at all. > :( > > > > Well, it would be a small list + expandos. :) > > This is a feature that is definitely causing severe pain to the > platform since it's putting constraints on APIs that we can add to our > main data model, the DOM. > > It would be really awesome if we could figure out a way to fix this. > I'd say the first step would be to evaluate if we actually need > expandos. And be prepared to break a few pages by removing support for > them. If we can agree to do that, then it's likely that we can create > a small object which forwards a short list of properties to the <form> > element (likely including the dynamic list of form element names) and > only put that object in scope. > Yes! I don't know how we can test this without just pushing out a release that does this and seeing what breaks though. Ojan
Received on Wednesday, 23 November 2011 00:46:11 UTC