On 25 Apr., 20:43, "T.J. Crowder" <[EMAIL PROTECTED]> wrote:
> Hi Thomas,
>
> I use Prototype 1.6 with FF without trouble, FWIW. What's the actual
> symptom you're running into? Are you sure you're using an
> unadulterated Prototype.js?
Hi T.J.,
in the broken line of Javascript I pasted you see that an opening " is
not closed, so the whole file from that point on gets borked.
I kind of expected it to work because otherwise the problem should be
known, but I don't get what breaks it here. I'm fairly sure the
prototype.js is unadulterated, because I extracted it form the jar
deployed in the Wicket app and it's the original. The mangling seems
to occur on its way from the jar to the browser.
Thanks,
Thomas
--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-spinoffs@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
