"All browsers include a "View Source" option, but none of them offer the ability to view the source code of external files. Most websites store their javascripts and style sheets in external files and then link to them within a web page's source code. Previously if you wanted to view the source code of an external javascript/stylesheet you would have to manually look through the source code to find the url and then type that into your browser.rnrnWell now there's a much easier way. You can use the JSView extension to solve the problem. You can access it from the context menu, from the toolbar, from the view menu, or from the status bar. If the website you are viewing contains any external js/css files, an icon will appear that says "SS", "JS", or both. Each individual file can then be viewed by clicking on the filename. The file will be opened in a new window. You can also choose to open all external files by clicking on "View All".rnrnWith the latest version you can now view the embedded css and js as well (FF2 and SM2 only). Just open the "Page Info" window from the context menu or tools menu. There will be 3 new tabs in that window. One for scripts, one for stylesheets, and one for frames. You can open them by double clicking or by using the context menu.rnrnYou can also right click on the 'view page source' menu item and open the url of the current page with jsview. This allows you to open the source code of any web page in a new tab or in an external editor."
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball NoScript FlashGot AdblockPlus
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.18) Gecko/20110320 SeaMonkey/2.0.13
I currently use JSView as well but I can see why it would be desirable and a feature that would be nice to have in NoScript, since we are already processing and intercepting stuff, its not that hard to populate a menu with access to it, even given the extra overhead and processing, it would reduce the overall overhead and surface by eliminating the need to add another addon when you can get the feature inside an already crucial and existing addon. Of course, it would take some work on Giorgio's part and that may not be on top of his priority list (and I don't fault him for it at all) and/or even something he might want to pursue but if he considers it, I am in support of it and would love to see it as well. As much as Fx prides itself on the ability to be "extended" with addons, its also its major flaw because the more you add, the more wrench you throw into the engine and the more breaks happen, the more overhead and memory leaks and eventually its so slow and useless that you might as well be on a 56k modem. Now its not "entirely" Mozilla's fault since the developers should be as disciplined and consistent as Giorgio to avoid such things but then again it doesn't do enough to standardize or keep consistent either and leaves the door open to asinine things happening.
~.:[ Lï£ê ï§ å Lêmðñ åñÐ Ì Wåñ† M¥ Mðñê¥ ßå¢k ]:.~ ________________ .: [ Major Mike's ] :. ________________
The compatibility info for JSView on AMO is bogus. It hasn't been updated for almost three years. The best and most current version is jsview-2.0.6-mod.xpi at http://xsidebar.mozdev.org/modifiedmisc.html#jsview
Mozilla/5.0 (Windows NT 5.1; rv:2.0) Gecko/20100101 Firefox/4.0