Re: [whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-12-01 Thread Boris Zbarsky
On 12/1/11 2:12 PM, Aryeh Gregor wrote: On Fri, Nov 25, 2011 at 11:06 PM, Boris Zbarsky wrote: It would break existing pages that use expandos on elements or documents via barewords in on* attributes. Isn't that the point of "look at element's named properties (if it has any)" and "look at el

Re: [whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-12-01 Thread Aryeh Gregor
On Fri, Nov 25, 2011 at 11:06 PM, Boris Zbarsky wrote: > It would break existing pages that use expandos on elements or documents via > barewords in on* attributes. Isn't that the point of "look at element's named properties (if it has any)" and "look at element's form's named properties (if it h

Re: [whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-11-29 Thread Boris Zbarsky
On 11/29/11 10:27 PM, Yehuda Katz wrote: Got it. Can we come up with a real-worldish example of someone using expandos with barewords? I'll look around. I recall seeing things like that somewhat recently, but I might be misremembering -Boris

Re: [whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-11-29 Thread Yehuda Katz
Yehuda Katz (ph) 718.877.1325 On Sat, Nov 26, 2011 at 12:42 PM, Boris Zbarsky wrote: > On 11/26/11 1:03 AM, Yehuda Katz wrote: > >> Honestly, before this discussion, I would have been surprised to hear >> that this works at all. It also seems to me that the group of people who >> know how to ad

Re: [whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-11-26 Thread Boris Zbarsky
On 11/26/11 1:03 AM, Yehuda Katz wrote: Honestly, before this discussion, I would have been surprised to hear that this works at all. It also seems to me that the group of people who know how to add an expando and the group of people who use onxxx= is pretty small to begin with. This isn't abou

Re: [whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-11-25 Thread Yehuda Katz
Yehuda Katz (ph) 718.877.1325 On Fri, Nov 25, 2011 at 8:06 PM, Boris Zbarsky wrote: > On 11/25/11 10:19 PM, Cameron McCormack wrote: > >> 1. if property name is in set S, then: >> a. look on element >> b. look on element's form (if it has one) >> c. look on document >> otherwise: >> a. look at

Re: [whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-11-25 Thread Boris Zbarsky
On 11/25/11 10:19 PM, Cameron McCormack wrote: 1. if property name is in set S, then: a. look on element b. look on element's form (if it has one) c. look on document otherwise: a. look at element's named properties (if it has any) b. look at element's form's named properties (if it has a form) 2

[whatwg] API design restrictions due to barewords in onxxx="" attributes

2011-11-25 Thread Cameron McCormack
This problem of using bare variables names rather than window.variableName in event handler attributes (which Boris mentions in https://developer.mozilla.org/Writing_Forward_Compatible_Websites) seems annoying. Is there any way we can avoid it by codifying current property lookup behaviour for