Hello, Thanks to this newsgroup, I've managed to get the context menu working of my port of the web-panels sidebar to Seamonkey. Now it's time to get the non-working menu items to actually do something.
Currently the back/forward menu items affect the main browser window, not the sidebar content. It looks like I may have to initialize history and set up a history listener. Any ideas on what is the minimum that is needed? I don't want to have to implement everything in navigator.js->Startup(). Also getBrowser() is hard coded to look for the main windows tabbrowser id. How do I generalize this to e.g. getThisBrowser() without having to resort to hard coding it to the id of the web panels browser? It might be useful for other extension authors who are using <browser> elements in their extensions. Thanks for any info about these problems. By the way <http://xsidebar.mozdev.org> now has a handful of Firefox sidebar extensions modded to work with Seamonkey. For the simpler extensions this was trivially easy. I'm really surprised that not more extension authors are making their extensions seamonkey compatible. For extension authors I would recomend the DevBoi sidebar off-line edition as it has standards documentation for CSS, HTML, DOM, and XUL. Not to mention the XULPlanet's XUL tutorial. Phil -- Philip Chee <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> http://flashblock.mozdev.org/ http://xsidebar.mozdev.org Guard us from the she-wolf and the wolf, and guard us from the thief, oh Night, and so be good for us to pass. [ ]General Failure reading drive A: Please remove your fist. * TagZilla 0.059 _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
