This add-on is an important one to me and tens of thousands of others as well. Sadly this very useful add-on and functionality is now gone from my FF as of 17.. Many people are downgrading or refusing to upgrade solely because it will break this add-on. In FF17 a major change was made to the function tosource's return value that broke not just this but many other add-ons as well. Now I don't have a problem with a change of standards and requiring everyone to update code to work with that. But this was handled in completely the wrong way by Mozilla IMO. Where is the support to the add-on community that has loyally supported your product all these years and giving them a proper chance to migrate/change code to work with the new function return values? Why was there no schedule with a phase-in plan and a deadline for such changes? Heck, a phase-in plan could have included a phase-in period where the function would support both methods by issuing an extra parameter for the new functionality. Then you could gradually switch the main return to be the new format. That way existing plugins would still be fine. It seems a bit horrible from an end user standpoint suddenly not having this great tool that improves the firefox experience so much. I know many others feel that same way about this add-on as i've seen countless comments about it, and i'm sure many others feel that way about add-ons that they use that also are now broken too. I'm writing here to ask either Mozilla to offer a fix, or the larger community to see if there is some workaround/middle ground that could be found. Perchance write a JS Function that could be included/injected into the broken add-ons that would convert/reformat the response of that function call so it remains usable to them with the data they need? I really hope someone can come up with some temp solution for everyone until more permanent ones can be developed. Thanks for reading..