On Jul 24, 12:22 pm, Tobie Langel <[EMAIL PROTECTED]> wrote: > Hi Andrew, > > You're misunderstanding a lot of different things here. > > I suggest you read the article "How Prototype Extends the > DOM":http://prototypejs.org/learn/extensions
The problem appears to be that the test in BrowserFeatures to know whether to set SpecificElementExtensions to true or false is returning "true" in Firefox 2.0.x.x. Therefore, in Element.extend, all of the code to actually perform the extensions are not called. "So?" you may ask. "Surely the point of the test is that the extensions don't need to be done; that's the whole point of that flag." Generally that's true - but what about when code in one document is called from code in another document, one which doesn't even include prototype.js? It is in exactly this case that I'm being affected by the behavior. My application involves a lot of iframes, and a *lot* of pages. We've only begun using prototype lately, so many legacy pages do not yet include prototype.js. When a call is made via a reference to "top" or "parent", things can go wrong. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
