I don't think the web search plug in itself will be the issue. More than likely it will be the trigger code. When the code obtains a trigger resource id from the OS, it stores the id in the trigger object. However, in the trigger's release code it asks the OS to remove the ID associated with the object, but it is somehow already nil. How it got this way or what other issues this could cause in other parts of the trigger code is unknown. Just a heads up for anyone that wants to take a dive into the trigger code.
BTW, Does the qss- web searches work as expected when not used as triggers? Marcel, the web search fixes mentioned were related to the displayed icons http://github.com/pkohut/blacktree-alchemy/commit/8112c8d9ff625688c3071e84ee188f16be242e85 and here some more info you might find useful http://github.com/tiennou/blacktree-elements/commit/9b2955f1f292c550e56d8275dfc54a9769cfe282
