Hey John, thanks for looking at this. Are the evals the only thing that AIR takes issue with, or does it "break the specs" in other ways? Yes, I ran into a few problems - I seem to remember it was with the $$ utility function, but I could be wrong... of course, now I've jquerified my script so I don't have the original Prototype version around. Tell you what, I'll play around with it tonight and post back then.
- Ben On Apr 4, 2:16 pm, John-David Dalton <[EMAIL PROTECTED]> wrote: > I tested the patch and it turns out that the eval() in the Selector > class isn't a problem becuase Adobe Air uses the compileXPathMatcher() > and bypasses the eval. The only issue must be the evals used for > scripting and the patch takes care of those as well. Other than that I > can't see an issue with my Tests. > Have yall had any issues or did you just assume Prototype wouldn't > work? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" 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/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
