Has anyone encountered this problem before?
A function which is attached to the window’s onLoad
with Event.observe crashes ie6 ONLY when appendChild is called.
I have confirmed it across multiple computers. Even weirder,
the function in question is a well tested script commonly used.
Hi
Rails AJAX controls are very handy, and the InPlaceEditor is probably
one of the easiest and most neat of them all. But, it doesn't do
autocompletion. I've rectified that situation. The plugin provides a few
new helpers and a new JavaScript-file that extends the
Ajax.InPlaceEditor with loc
On 7/22/06, Todd Ross <[EMAIL PROTECTED]> wrote:
I, personally, would rather see you opening bugs and submitting patches
to eliminate the inefficiencies that seem to make you so uncomfortable.
When Rails trac is stable, capable of accepting new tickets, and there
is sign of daily activity in P
On 7/22/06, Brandon Aaron <[EMAIL PROTECTED]> wrote:
Seriously Perter, just keep it to one thread at least.
Fair enough. It was a genuine question. I'm not a troll or a jerk. I
haven't tried to insult anyone.
You already know the answer. Same answer as pretty much everyone else on this
list
On 7/22/06, Todd Ross <[EMAIL PROTECTED]> wrote:
You responded to one of my messages twice. Once on 07/19 and again on
07/22.
I had another idea
Are you just sitting there stewing over the fact that people
disagree with you?
No. It is not about disagreeing at all.
I think Prototype is
script.aculo.us sure is actively maintained.
I consider most stuff in it working pretty nicely (although there
are a few patches waiting, I know, I know), so I don't feel there's much
pressure to do rush out a new release. Plus, I'm pretty stuffed with
a huge project here.
Anyway, I should have
>>Can I trouble you to add a comment to the bug so that others are aware
>>of the problem? Someone might post an alternative patch then as well.
>>http://dev.rubyonrails.org/ticket/3730
Done.
Thanks,
Mandy.
___
Rails-spinoffs mailing list
Rails-spinoff
Maninder, Singh wrote:
> Your solution doesn't work in Safari.
>
> As per the Gentleman who helped me test this, after aborting
> the request, onComplete is not getting fired in Safari.
I'm sorry to hear that but thanks for the report! I don't have access
to a machine with Safari, I'm afraid.
C
Peter Michaux wrote:
> On 7/19/06, Todd Ross <[EMAIL PROTECTED]> wrote:
>> Peter Michaux wrote:
>> > On 7/19/06, Todd Ross <[EMAIL PROTECTED]> wrote:
>> >
>> >> but I still believe in Prototype-the-project.
>> >
>> > I'm curious why.
>>
>> I've already eluded to the why. Its the cleanest, most ele
Todd,
Your solution doesn't work in Safari.
As per the Gentleman who helped me test this, after aborting the request,
onComplete is not getting fired in Safari.
We have put a hack round it by explicitly calling it after aborting.
But, just wanted you to be in the loop.
Thanks for a great patc
Seriously Perter, just keep it to one thread at least. You already know the answer. Same answer as pretty much everyone else on this list.On 7/22/06, Peter Michaux
<[EMAIL PROTECTED]> wrote:
On 7/22/06, Chris Chabot <[EMAIL PROTECTED]> wrote:> prototype is the> base I prefer to use for my web appl
Although I do not agree with you anywhere else on your thoughts about prototype. Abstract.Insertion is the first thing I removed and replaced with a few methods on Element.Methods. Like, prependChild, insertAfter, insertAtIndex. They make more sense to me to be in
Element.Methods instead of their
On 22/07/06, Peter Michaux <[EMAIL PROTECTED]> wrote:
But I would say they make your client-side pages less efficient,
robust and maintainable.
But, you would be wrong, sorry.
--
Andrew Tetlaw
htp://tetlaw.id.au
___
Rails-spinoffs mailing list
Rails
On 7/19/06, Todd Ross <[EMAIL PROTECTED]> wrote:
Peter Michaux wrote:
> On 7/19/06, Todd Ross <[EMAIL PROTECTED]> wrote:
>
>> but I still believe in Prototype-the-project.
>
> I'm curious why.
I've already eluded to the why. Its the cleanest, most elegant
JavaScript code base that I've ever lai
On 7/22/06, Andrew Tetlaw <[EMAIL PROTECTED]> wrote:
Prototype-style expressions match the way I think and make
me more productive.
But I would say they make your client-side pages less efficient,
robust and maintainable. All this for how much extra productivity? A
few extra key strokes saved
On 7/22/06, Chris Chabot <[EMAIL PROTECTED]> wrote:
prototype is the
base I prefer to use for my web application client side scripting,
Why?
___
Rails-spinoffs mailing list
Rails-spinoffs@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/list
I have to admit I'm a little worried about the question whether I should
consider script.aculo.us to be 'maintained' or not.
A long time ago there was movement to release 1.6.2, and there's a few good
bugfixes in the trac bug database, but not a whole lot of movement seems to
be happening anymore,
On 20/07/06, Peter Michaux <[EMAIL PROTECTED]> wrote:
On 7/20/06, Thomas Fuchs <[EMAIL PROTECTED]> wrote:
> The sole point of Prototype is to give the programmer a powerful,
> opinionated
> toolset, to make programming JavaScript less pain
That is a great idea but unfortuntely, prototype.js end
18 matches
Mail list logo
