Just passing along some info regarding this problem:
It's a lil hard for me to tell exactly why the problem occurred.
I had some previous custom javascript code for OO programming and
inheritance where I defined new methods on Object.prototype and
Function.prototype (from Shelby H. Moore). Those worked fine with
prototype 1.5, but for some reason, these new methods appeared to
conflict significantly with prototype 1.6. Since I didn't have tons of
time to spend on the issue, and since the new prototype includes a
pleasant solution to OO programming and inheritance, I just removed my
methods, updated the code I had with classes and the problem went
away.
On Jan 11, 4:09 am, Wizz <[EMAIL PROTECTED]> wrote:
> On 10 jan, 18:37, Frank <[EMAIL PROTECTED]> wrote:
>
> > Using prototype 1.6.0
>
> > Tried all these variants:
>
> > someelement.insert(sMessage);
> > Element.insert(someelement, {bottom:sMessage})
> > newInsertion.Bottom(someelement, sMessage);
>
> > And always get an exception thrown by the method call. someelement is
> > a valid and existing div and sMessage is just a string. Looks like a
> > bug to me, but maybe I'm using it wrong?
>
> > Any and all help appreciated.
>
> Do you have a live testcase for us or some code we can try out? It's
> pretty hard to debug something that should just work, even more when
> it's such a simple case...
>
> Greetz,
>
> Wizz
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
