No; you're correct. If I don't include the other JS in the page,
prototype is fine. That makes me feel better about that one.
Unfortunately, the other JS is just also important. But, it let me
know that the problem was elsewhere. That led me to find out that the
problem was the following:
$w("html body").each(function(el) { $$(el)[0].setStyle({ ... }); });
IE7 is chocking in the each() function call which is why the debugger
opened prototype.js rather than my code.
Thanks, kangax.
On Jan 23, 3:36 pm, kangax <[EMAIL PROTECTED]> wrote:
> David,
>
> Are you saying that IE throws an error with only prototype.js included?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
