[WASP] minor bug fixes - v0.32
I decided to do another quick release of WASP to fix minor issues.
Getting it or upgrading
Three easy ways to upgrade or get WASP:- Visit wasp.immeria.net and click on the large "Download" button
- If you already have WASP, the easiest way to upgrade is simply to do "Tools/Add-ons" from the Firefox menu, then click on the "Find Updates" button.
- Alternatively, if you already have WASP installed, Firefox will eventually trigger an automatic update and prompt you to confirm.
New & improved
Here's whats new and enhanced in v0.32:- Improved: There's one major change in this release: WASP now looks at the HTTP GET rather than the RESPONSE. A bit technical, but what this means is a slightly better detection. I was also able to further optimize then detection algorithm.
- Improved: WASP was already handling Google Analytics (GA code) and Google Analytics (Urchin code) and now offer better handling of Google Website Optimizer.
- Improved: For Omniture SiteCatalyst and Google Analytics, there's now a quick-help that shows when you click on one item from the tree.
- New: Now detects 77 solutions including WysiStat, TNS Metrix, ProspectXtractor, m-pathy.


2 comments:
I found a potential bug with WASP that has been driving me nuts.
In Firefox I frequently use the Ctrl+t key combination for a new browser tab. The default action in Firefox when this happens is to place the input focus on the address/location bar. When WASP 0.32 is installed this is not the case. The user is thus required to use Ctrl+t then Ctrl+l.
I have tested this by disabling each add-on and turning each one on, one by one. WASP 0.32 is the only add-on in my installation that acts improperly.
That's really strange, I have tried to reproduce what you describe and it always put the cursor in the address/location bar as it should. For sure, I don't have any code to do cursor re-positioning, so it would be a default behavior of Firefox.
Post a Comment