I ever liked this addon, it saves me some time and detects some libs (or sometimes detects libs) when Wappalyzer doesn't. But now I'm facing an annoying bug: When customizing my toolbars, I accidentally moved this addon's pseudo-button from addon (status) bar to the main toolbar next to the address field. And now I cannot move it from there - any other button but it is movable. I don't need it there, I wish it back to status bar! Uninstalling and re-installing the addon doesn't solve the problem: the button re-appears at the same place and is still unmovable :(
How to update. 1. Save link as. 2. Open the .xpi with winrar,7zip, or whatever you use. 3. Open the install.rdf no need to extract it since it can be opened with notepad. 4.At line 17 which reads 3.6.* Change the 3.6.* to whatever you're using no need for the second . or *. Example 20.0
The * can be used though it's for wildcards. I usually put 20.0*
This seemed like a nifty idea, so I installed this plugin. Later, I noticed a website I am working on was behaving strangely w/ postdata. Data appeared to be posted twice.
Traced the problem back to this plugin -- it loads every page twice, even if it's a POST request.
This seems like bad design, I do not want my forms re-submitted. Hopefully it at least doesn't do this on SSL sites, otherwise ppl will be doing a double-submit & possibly charging credit cards twice.
I've uninstalled this plugin since, it's a cool idea, I like to know what libraries are used at a glance, but there needs to be an option to disable the plugin for postdata.
Maybe a simple 'unloaded' icon can appear on POST sites, which requires a click/confirm before loading the list of plugins & re-submitting the form. Even the browser has built in protections requiring you to confirm before resubmitting POSTs, it's just not a good idea.
I tried to find out if that's really the case, but couldn't reproduce it. In fact, I don't even know how that should happen, because the plugin's source code is incredibly simple and not modifying the actual loaded page at all.
It's completely passive, just listens to the load and tabchange events, and then checks the window object if some library has been found.