Is their bug tracking publicly available? We really like the product
and are considering using this in our Intranet environment, but cannot
move forward without this key feature implemented.
On Nov 15, 2:54 am, "Alex Mcauley" <[EMAIL PROTECTED]>
wrote:
> its a known bug in Chrome .. i reported th
On Nov 15, 10:26 pm, Namotco <[EMAIL PROTECTED]> wrote:
> I was trying to demonstrate my problem, it's not what's actually in my
> code. It's seems that $('test') inside my eval is not the same as the
> $('test') outside of it. When I try to run that code I'd expect $
> ('test')'s HTML to change
I was trying to demonstrate my problem, it's not what's actually in my
code. It's seems that $('test') inside my eval is not the same as the
$('test') outside of it. When I try to run that code I'd expect $
('test')'s HTML to change, but it doesn't. Why not and how can I make
it do that?
--~--~
Look at this article:
http://weblogs.asp.net/infinitiesloop/archive/2008/11/09/asp-net-ajax-4-0-observing-updates-to-pojos-plain-ole-javascript-objects.aspx
may be its a good idea to be implemented in prototype core?
--~--~-~--~~~---~--~~
You received this message
> ...unfortunately many of our
> clients use old Macs with IE 5.5.
Wow. Microsoft announced they were going to EOL it in 2003, and did
so in 2005. That's a _long_ time to keep using a browser that's not
even getting security patches... They only use it for sites they know
and trust, right? ;-)
Alex,
You're incrementing and decrementing Ajax.activeRequestCount, which is
already being maintained by Prototype. Look again at the docs[1], it
tells you that it's doing that. Hence your getting odd results. If
you want to just use Ajax.activeRequestCount, you can do that; or if
you want to
Not yet Kangax, I will try to upgrade that and see what happens...
Thanks!
On Nov 13, 8:47 pm, kangax <[EMAIL PROTECTED]> wrote:
> On Nov 13, 5:29 pm, Nilavan <[EMAIL PROTECTED]> wrote:
>
>
>
> > Hi,
> > I am not very knowledgeable in Javascript but I am using the Prototpye
> > framework in one o
Really Easy Example:
new Effect.Fade('link', { duration: 0.2, afterFinish:
function()
{
new Effect.Show('link',{duration:0.2});
}
});
its a known bug in Chrome .. i reported the issue a few weeks ago ...
It also happens when watching multiple classnames and invoking them
Something like
$$('.someClass').invoke('observe','click',function(e) {
alert('Clicked me');
});
1
2
3
4
5
will only observe the last element wit
