Any library, like Prototype, that changes the Javascript type system will cause you great pain if used in an extension. The entire browser's javascript gets modified when you do that.
John On Oct 9, 11:14 am, Curtis <[EMAIL PROTECTED]> wrote: > I am having an issue with Firebug when I include Prototype.js in my > Firefox extension. If I include Prototype using <script/> in the main > XUL then Firebug's view/inspect HTML doesn't function correctly. > Viewing the source displays a blank pane and inspecting the source > displays the DOM elements (as if the DOM tab was selected) instead of > the inspected source. > > Has anyone seen this issue? I've read several places that Prototype > does some not-so-nice things in terms of extending core Javascript > objects (which has gotten better with their newer versions) but I > couldn't find any examples of people having issues with Prototype and > Firebug. > > Firefox 3.0.3 > Firebug 1.2.1 > Prototype.js 1.6.0.3 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" 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/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
