Ulasan untuk ContextSearch web-ext
ContextSearch web-ext oleh Mike B
Tinjauan oleh thuerrsch
Diberi peringkat 4 dari 5
oleh thuerrsch, 7 tahun yang laluNice replacement for the old Context Search add-on which I started to miss bitterly right after Firefox 57 came out. Something like this should REALLY be standard in Firefox.
That said, getting the add-on to work in "Automatic" mode on GNU/Linux (Ubuntu, in my case) was a bit of a hassle. The instructions on the GitHub site could be more helpful here. They put too much focus on the location of ContextSearch.json (no, DON'T put that file or anything else under /usr/lib/ or /usr/lib64/, these are to be maintained by your package manager alone) and leave more important points unmentioned.
To make a long story short, I had to do the following:
(1) Put ContextSearch.json and ContextSearch.py from the git repository into ~/.mozilla/native-messaging-hosts/.
(2) Make ContextSearch.py executable (chmod u+x) AND convert it from CR/LF (Windows) to LF (Unix) line endings so that python can actually run the script. (I also changed the shebang to #!/usr/bin/env python).
(3) Change the path value in ContextSearch.json to the actual location of ContextSearch.py (why doesn't it just default to ContextSearch.json and ContextSearch.py being in the same directory?).
(4) Enter the path of my search.json.mozlz4 file in the add-on's preferences.
And hey not-quite-presto, everything works! Well, apart from a few details, like search engines using POST rather then GET requests not working but showing up in the context menu. All in all, a promising extension with a few rough edges.
That said, getting the add-on to work in "Automatic" mode on GNU/Linux (Ubuntu, in my case) was a bit of a hassle. The instructions on the GitHub site could be more helpful here. They put too much focus on the location of ContextSearch.json (no, DON'T put that file or anything else under /usr/lib/ or /usr/lib64/, these are to be maintained by your package manager alone) and leave more important points unmentioned.
To make a long story short, I had to do the following:
(1) Put ContextSearch.json and ContextSearch.py from the git repository into ~/.mozilla/native-messaging-hosts/.
(2) Make ContextSearch.py executable (chmod u+x) AND convert it from CR/LF (Windows) to LF (Unix) line endings so that python can actually run the script. (I also changed the shebang to #!/usr/bin/env python).
(3) Change the path value in ContextSearch.json to the actual location of ContextSearch.py (why doesn't it just default to ContextSearch.json and ContextSearch.py being in the same directory?).
(4) Enter the path of my search.json.mozlz4 file in the add-on's preferences.
And hey not-quite-presto, everything works! Well, apart from a few details, like search engines using POST rather then GET requests not working but showing up in the context menu. All in all, a promising extension with a few rough edges.
Balasan pengembang
dikirim 7 tahun yang lalu(edit3)
Can you tell me which POST engines aren't working? I'll take a look.
1.2.1b6 in the beta section fixed a bug where {searchTerms} in POST was only replaced in the form params and not if it was also included in the url params. If that was causing your issues, give the beta a try.
I've updated the readme at github to better reflect your experience setting up the python script. Let me know if there's anything else that would be helpful for other users installing the native app
(edit)
The instructions to put the .json in /usr/lib or /usr/lib64 were taken directly from the Firefox documentation for the native app API. On the chance you see this edit, would you mind opening a ticket at github and elaborating on why this incorrect?
(2) Hmm, yeah that probably should be in Unix (LF) Oops, I'll update
(3) That's what the Firefox Native Messaging API requires. Nothing I can do there.
Glad to hear you got it working. You might be the first that used the python script. Guess I'll have to keep it updated :(
Can you tell me which POST engines aren't working? I'll take a look.
1.2.1b6 in the beta section fixed a bug where {searchTerms} in POST was only replaced in the form params and not if it was also included in the url params. If that was causing your issues, give the beta a try.
I've updated the readme at github to better reflect your experience setting up the python script. Let me know if there's anything else that would be helpful for other users installing the native app
(edit)
The instructions to put the .json in /usr/lib or /usr/lib64 were taken directly from the Firefox documentation for the native app API. On the chance you see this edit, would you mind opening a ticket at github and elaborating on why this incorrect?
(2) Hmm, yeah that probably should be in Unix (LF) Oops, I'll update
(3) That's what the Firefox Native Messaging API requires. Nothing I can do there.
Glad to hear you got it working. You might be the first that used the python script. Guess I'll have to keep it updated :(
196 ulasan
- Diberi peringkat 5 dari 5oleh Den, 18 hari yang laluA great replacement for the defunct Swift Selection Search
- Diberi peringkat 5 dari 5oleh Piper, 22 hari yang lalu
- Diberi peringkat 5 dari 5oleh Gemini62167, sebulan yang lalu
- Diberi peringkat 5 dari 5oleh Rage, 2 bulan yang laluDear Author, I'm Japanese, so please excuse my poor English.
If the version is v1.47.1 or later, Japanese character codes such as "shift_jis" and "euc_jp" cannot be used because they garble the text.
There seems to be a problem with sending from a Unicode site to a JIS site. It seems that the text is sent as utf_8 without being converted.
I rolled back to v1.46.26 and there are no problems.
(The same situation occurs with Chrome.)
PS: I don't have a Github account, so I reported this problem here. - Diberi peringkat 5 dari 5oleh HypnotizedNarcissist, 3 bulan yang laluthe best from the best
my respect mike
easy, fast, great lay-out, top add-on
thank you very much
btw. and always good updates - Diberi peringkat 5 dari 5oleh Кадочников Сергей, 4 bulan yang laluПрекрасное расширение, удобное, легко настраиваемое под себя.
- Diberi peringkat 5 dari 5oleh Seän "Frostbyte" Shepherd, 5 bulan yang lalu
- Diberi peringkat 5 dari 5oleh EarOfWheat, 6 bulan yang lalu
- Diberi peringkat 5 dari 5oleh darlington95, 6 bulan yang lalu
- Diberi peringkat 4 dari 5oleh Dideldum, 7 bulan yang laluDefinitely the Best Search-addon. Nearly perfect.
Unfortunately the sidebar feature is not working (Firefox & Chromium).. - Diberi peringkat 5 dari 5oleh Seän D. Shepherd, 7 bulan yang lalu
- Diberi peringkat 5 dari 5oleh Ninetynine, 8 bulan yang lalu
- Diberi peringkat 5 dari 5oleh Dom0909, 9 bulan yang lalu
- Diberi peringkat 5 dari 5oleh Pengguna Firefox 10244801, 10 bulan yang laluDitched my two faithful companions Context Search Origin and Swift Selection Search when I found this babe.
- Diberi peringkat 5 dari 5oleh biggsley, 10 bulan yang lalu
- Diberi peringkat 5 dari 5oleh Isaac, 10 bulan yang laluThis is actual software in the form of an Add-On. Aces job!
- Diberi peringkat 5 dari 5oleh Saud, setahun yang lalu
- Diberi peringkat 1 dari 5oleh LawrenceSan, setahun yang laluI've used many, many different extensions in several different browsers over many years. (I'm an experienced web developer, starting when the web was first invented, and can code several different web languages -- in other words, I'm not a newbie.)
ContextSearch web-ext has the most complicated, buggy preferences interface I've ever seen in a browser extension. I have it running in both Firefox and Chrome, and when it works it's great -- but trying to customize it, add search engines, etc. is a nightmare.
Currently one of the engines in my ContextSearch list is "Google Maps". It works fine in Firefox, but doesn't work at all in Chrome, just leads to a blank page. So I tried exporting it from Firefox into Chrome. Forget it! The export/import features in the extension's customization interface appears to just export the URL for the icon, not for the search engine itself? And some of the gazillion preferences-interface elements for this extension, in both browsers, appear as just solid gray blocks -- regardless of what theme I use, or whether Dark Reader is on or off, or what other interface options I choose for ContextSearch itself. Of the options (including links) that I can see clearly, most of them don't do anything like what their name implies or what I'd expect them to do.
I haven't given up on it because, for the engines I finally get working, it's very useful. But I spend more time wrestling with this interface than with all my other (many) installed extensions put together! - Diberi peringkat 5 dari 5oleh Pengguna Firefox 5599219, setahun yang lalu
- Diberi peringkat 5 dari 5oleh Pengguna Firefox 12680106, 2 tahun yang lalu
- Diberi peringkat 5 dari 5oleh XacK, 2 tahun yang laluGreat add-on
Lacks the option to "Close menu on right click" Balasan pengembang
dikirim 2 tahun yang lalu(edit) That bug has been found and will be fixed in the next release
The save bug is known and may have been addressed in a recent version. I know it's been a persistent annoyance.
As for the transparency, you should be able to set that yourself using CS Options -> General -> User Styles. Use CSS selectors to apply opacity levels to the menu. If you need help, open an issue at the github site.- Diberi peringkat 1 dari 5oleh mimigu, 2 tahun yang laluVersions after May no longer work. I would like to downgrade to an earlier version but can't find it.
Balasan pengembang
dikirim 2 tahun yang laluYou can find older versions here https://addons.mozilla.org/en-US/firefox/addon/contextsearch-web-ext/versions/
But depending on what when wrong, that may not fix your problems. If you could elaborate on the issue, either here or at the support site, I'd be happy to go over some troubleshooting with you. https://github.com/ssborbis/ContextSearch-web-ext - Diberi peringkat 5 dari 5oleh bezuma, 2 tahun yang lalu
- Diberi peringkat 5 dari 5oleh Alwaysliumx, 2 tahun yang lalu