I think he meant it as a workaround, not as a bug fix.
Thanks, David!
Cheers,
Andrew
On Jan 10, 11:06 am, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> In other words, you eliminated the cache?
> We would rather fix the problem than lose the cache (and the speed increase
> it provides). You co
In other words, you eliminated the cache?
We would rather fix the problem than lose the cache (and the speed increase
it provides). You could first try and checkout the library from Subversion
(described on prototypejs.org/contribute), create the build and open
test/unit/dom.html in Mozilla. If the
On Oct 19, 6:58 pm, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On 10/19/07, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
>
>
> > That being said, this is my drop-in replacement:
> > ...
>
> Viktor,
>
> After giving it a second thought, I realize that the general direction of
> your solution
On 10/19/07, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
>
> That being said, this is my drop-in replacement:
> ...
Viktor,
After giving it a second thought, I realize that the general direction of
your solution might not be so bad. After all, this is only IE we are talking
about -- other bro
Don't we have _attributeTranslations in IE?
$H(Element._attributeTranslations.read.values).keys().include('onion'); //
=> false
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Prototype: Core" group.
To post to th
On 10/19/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
>
> On 10/19/07, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
> >
> >
> > new Element('div', {onclick: 'alert(this)'});
>
>
> I don't think any of us is interested in making this work.
I'm sorry, what I meant to say is that I'm not really in
On Oct 19, 5:15 pm, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On 10/19/07, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
>
>
> > Mislav, the problem is not whether you are interested in making this
> > work or not, the problem is that `new Element' doesn't behave like a
> > 'prototype' fun
On 19/10/2007, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
> On 10/19/07, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
> >
> > Mislav, the problem is not whether you are interested in making this
> > work or not, the problem is that `new Element' doesn't behave like a
> > 'prototype' function, since
On 10/19/07, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
>
> Mislav, the problem is not whether you are interested in making this
> work or not, the problem is that `new Element' doesn't behave like a
> 'prototype' function, since it's not consistent across browsers.
So, to make it work in IE
On Oct 19, 4:43 pm, "Richard Quadling" <[EMAIL PROTECTED]>
wrote:
> On 19/10/2007, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > This is a really troublesome bug, which is exhibited in IE browsers.
> > Consider this code:
>
> > new Element('div', {onclick: 'alert(this)'});
>
> > In ev
On 10/19/07, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
>
> This is a really troublesome bug, which is exhibited in IE browsers.
> Consider this code:
>
> new Element('div', {onclick: 'alert(this)'});
I don't think any of us is interested in making this work. I second what
Tobie said.
--~--~
On 19/10/2007, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
>
> This is a really troublesome bug, which is exhibited in IE browsers.
> Consider this code:
>
> new Element('div', {onclick: 'alert(this)'});
>
> In every other browser, this will produce a div, that, when clicked,
> will alert. In IE,
Hey Viktor,
This syntax is just not supported at the moment.
Use:
new Element('div').observe('click', callback);
instead.
Regards,
Tobie
On Oct 19, 2:37 pm, Viktor Kojouharov <[EMAIL PROTECTED]> wrote:
> This is a really troublesome bug, which is exhibited in IE browsers.
> Consider t
13 matches
Mail list logo
