![]() ![]() var firebug=doc.createElement('script') frun.innerText = 'javascript:firebug.init()' var frun=document.createElement('script') Var firebug=doc.createElement('script') tAttribute('src','') (firebug) Here is my Command bar button script so far. Think I have a Command Bar button ready to go. ![]() I think (from memory) there are some IE8 specific issues also. You can easily convert the Firebug scriptlet to a Command Bar button or menu extension script, but it does not work in framesets and can be blocked (depending upon the security zone of the current site). No that wont work for XMLHTTP requests as showing a Modal context menu stops scripts running on the current document. From the modal dialog you can apply changes back to the calling (external) document. You need a modal dialog (and hence I think the best type of Addon to use is a modal context menu extension) because there is not scripting api to hook back into the IE chrome to determine when the current tab changes. In your existing firebug.js you replace references to the document object with First up, define your IE window and document variables from the external object var win=nuArguments var doc=win.document Sinking events into IE from another window (panel) is different. That would work as soon as the page starts to parse or as soon as the user uses a context menu?Ĭontext menus, Command Bar buttons and menu extensions have access to the external object and can hook into it. But baby steps first, unless someone has created UI panels in an IE addon that are built from standard HTML/js/css and could shed some light on the subject.Īs for your method of sinking event listeners. We may move to a commonjs form in order to normalize and package it's various parts. I would guess that we would create a COM component that would load up the Firebug JS into the context of the page, though the more ideal solution would be to create a panel in IE to host HTML and load the firebug code in there as is done in gecko. Context menus are unaffected also by Addons settings. Note that the IE Developer Tool does not appear in the IE Addons list and so is still loaded if all Addons are disabled. Good developers test their pages in FX and others anyway. ![]() You can then use the nuArguments to build your trees etc and sink your eventlisteners. Either convert to a COM addon or a Context menu extension that uses the show in modal dialog switch. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |