> It's not a "bug" per se. > > jQuery makes the assumption that a global variable exists named > 'document' and that it refers to the containing document element. > > This is not true in all cases where jQuery might be used - like in a > FF add-on, for example. In the example posted, the code is passed a > reference to the document object. Since jQuery assumes that 'document' > is a global reference to the document, anywhere it is used will break. > > The solution is simple - instead of directly referencing 'document' in > the jQuery code, create a jQuery variable that references the > document. Any code not in the expected environment can change it as > needed.
I'm well aware of the issue - we've discussed it a number of times on this list. However, what we've done is try to enforce the proper context wherever we can (grabbing the .ownerDocument, for example). I wasn't aware of outstanding issues in that regard. I'd much rather fix those bugs from the get go since it would make jQuery that much more able to handle multiple contexts, to begin with. --John --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
