"There is no possible selective search on multiple sites at the same time. Bullshit!"

There are a number of ways to search multiple sites at the same time.

Folder search -> Search every engine in a particular folder with one click.

When using the context menu, enable "Show an option to search the entire folder at the top of the menu". This places a menu entry that allows searching every engine in the folder.

When using one of the tile-based menus, map a mouse button to a folder search action under Quick Menu -> Search Actions. Tile-based menus also allow for clicking several engines, one after the other, while keeping the menu open, whereas the context menu does not.

You can also create a new engine with multiple URLs in the template field. Simply enter them as a javascript array, i.e. ["http://somewebsite/q={searchTerms}", "http://someotherwebsite/search/{searchTerms}"]

Существует несколько способов одновременного поиска на нескольких сайтах.

Поиск в папке -> Поиск в каждом движке в определенной папке одним щелчком мыши.

При использовании контекстного меню включите «Показать параметр для поиска во всей папке вверху меню». Это помещает пункт меню, который позволяет искать каждый движок в папке.

При использовании одного из меню на основе плитки сопоставьте кнопку мыши с действием поиска в папке в меню «Быстрое меню» -> «Действия поиска». Меню на основе плитки также позволяют щелкать несколько движков один за другим, оставляя меню открытым, тогда как контекстное меню этого не делает.

Вы также можете создать новый движок с несколькими URL-адресами в поле шаблона. Просто введите их в виде массива JavaScript, например ["http://somewebsite/q={searchTerms}", "http://someotherwebsite/search/{searchTerms}"]

Thanks. I've found the problem based on the links you provided.

The clipboard API requires a secure HTTPS website to function. The first link you provided uses HTTPS on the main page, but not on the results page. I assume it's the same issue you're having on your local server ( no https ).

I've added some fallback code that seems to work, but the function is long depreciated, and may stop working at some point. Fixes will be in the next release.

👍 sorry I didn't see your edit sooner. I have a fix ready and will have a new release soon

I think this bug may have finally been tracked down, with the help of a user @ the github support site. If you're game, backup your current CS config and install the signed pre-release from here: https://github.com/ssborbis/ContextSearch-web-ext/releases/tag/v1.32a1

See if 1.31.8 or above fixes your issues.

It should work fine. Make sure you're on the latest version. v1.31 was a bit of a mess

"The extension is good, but a message constantly pops up on a yellow background at the top of the screen stating that this add-on slows down the loading of web pages"

The only time I've seen real slowdown is during the marking of very short search results on a large page or using the Find bar to search across all tabs. When are you seeing the slowdown?

(edit3 - 10-19-2020) Were you searching a folder or a single engine when you observed the problem last? I've uploaded v1.27.5 which fixed the same problem v1.27.4 did, but when searching a folder as well.

(edit 2) Thanks for the reply. I thought the bug fixed in 1.27.4 would take care of your issue, but there must be another bug. I've tried all the engines you mentioned, but I'm getting good search results using the context menu now. Could you open ContextSearch options -> Search Engines and tell me if you see an orange (FF) next to those engines you're having issues with? If not, could you edit one of them and paste the template / method / etc info? It could help narrow down the problem.

(edit) Nevermind, version 1.27.4 going up. Context menu was not working with Firefox engines

Would you mind opening a ticket at the support site or editing your reply here? Some users seem to be experiencing problems with the latest builds and I could use some input on what exactly is going wrong. I tried adding Yandex to my install and had no problems, and troubleshooting is difficult when I can't replicate the bug.