[Prototype-core] Re: Ticket 10030 - is Ajax.Request.success() broken?

2007-11-13 Thread Tobie Langel
Hi Ken, Thanks for the extended research. That's really helpful! Could you please clarify what kind of errors FF is throwing ? Also, could you please kindly advise if Safari 2's behaviour is consistent with Safari 3 ? Thanks, Tobie On Nov 14, 12:27 am, Ken Snyder <[EMAIL PROTECTED]> wrote: >

[Prototype-core] Re: Ticket 10030 - is Ajax.Request.success() broken?

2007-11-13 Thread Ken Snyder
Tobie Langel wrote: > Some browsers - I can't remember witch - always return a status of 0 > for the file: protocol, others don't return a value at all in that > case, hence this hack. > > We're going to be doing more work on Ajax for 1.6.1, but I'm not even > sure there is a real solution ot his

[Prototype-core] Re: PeriodicalExecuter : proposal for upgrade

2007-11-13 Thread Mislav Marohnić
Hey Pascal, It's a big change for a small feature that most of the people won't need. But why don't you take a look at http://dev.rubyonrails.org/ticket/9370, where I posted a small patch to get PeriodicalExecuter#restart method. On Nov 13, 2007 9:35 PM, pvk <[EMAIL PROTECTED]> wrote: > > > I am

[Prototype-core] Improving document.viewport.getDimensions()

2007-11-13 Thread Nick Stakenburg
I'm hoping document.viewport.getDimensions() can be improved. At the moment I'm using a patched version in Prototip to keep tooltips within the viewport, as it works better then the method from trunk. Mootools uses a similar approach. To point out the issues in the current function I've added uni

[Prototype-core] PeriodicalExecuter : proposal for upgrade

2007-11-13 Thread pvk
I am in need of a PeriodicalExecuter that I would start and stop regularly and quite a lot. The doc tells me that I should create a new one each time, but it doesn't looks like good memory management practice to me. So here is a proposition for an upgrade to PeriodicalExecuter (note that I am o

[Prototype-core] Re: Ticket 10030 - is Ajax.Request.success() broken?

2007-11-13 Thread Tobie Langel
Some browsers - I can't remember witch - always return a status of 0 for the file: protocol, others don't return a value at all in that case, hence this hack. We're going to be doing more work on Ajax for 1.6.1, but I'm not even sure there is a real solution ot his issue. Regards, Tobie On No