benbasson / contextsearch

Firefox Extension - Context Search transforms the "Web Search for..." context item into a menu containing your Firefox Search Providers. This is very convenient, since it allows you to decide which search engine you use. Firefox's default is to use the currently selected search provider only.
http://www.basson.at/firefox-addons/contextsearch
Other
36 stars 5 forks source link

Firefox 57+ / WebExtensions version? #33

Open CaptaPraelium opened 6 years ago

CaptaPraelium commented 6 years ago

Hi there,

Such a useful addon, it would be a shame to lose it soon. Do you have any plans for a WebExtensions version of this?

seiferflo commented 6 years ago

Got my vote as well ! Firefox limits to default search engine only.

Hlsgs commented 6 years ago

+1

benbasson commented 6 years ago

Sorry, it's not going to happen any time soon. Mozilla haven't implemented an API to provide access to the installed search engines, which is like 90% of the functionality of this add-on.

https://bugzilla.mozilla.org/show_bug.cgi?id=1352598 is the blocker. According to comments, unless "someone" contributes the change, which I do not have the time or patience for, then it certainly isn't being added before Firefox 59.

Feel free to vote for that bug, but don't add comments unless you're willing to actually help the feature get implemented (Bugzilla isn't the place for moaning about this, feel free to complain to Mozilla via any other means).

benbasson commented 6 years ago

If Mozilla manage to provide this API sometime in the next couple of months I'll revive the add-on. If it takes longer, it's possible I will lose interest. By that time this add-on will probably lose most of its 30,000 users anyway. I guess we'll see.

bege10 commented 6 years ago

For those who want to stay with this extension (and the many other extensions that don't work with Firefox 57+): Context Search 0.6.4 works with Waterfox, Context Search 0.6.3 with Palemoon.

benbasson commented 6 years ago

I'm sorry, I cannot agree with your recommendation.

If you're looking for an alternative browser to support this functionality, I would suggest switching to Vivaldi (which supports Chrome add-ons) or Chrome, both of which have an equivalent add-on, and have the benefit of being supported by proper companies.

Waterfox and Palemoon might be based on Mozilla source code, but I do not trust these small third-party forks enough to recommend them, e.g. in terms of security patching and reaction to zero-day vulnerabilities.

If you're keen on remaining with Mozilla, then use the Firefox 52 ESR which will be supported (and existing add-ons will work with it) until June 2018. I would hope that I'll have a replacement version released by then.

Hlsgs commented 6 years ago

@benbasson agreed. I would add that, painful as it may be, the process that FF is going through is well worth the effort, if the browser is to remain relevant. And FF's userbase shouldn't abandon ship because of such minor inconveniences, but rather remain loyal, again, if the browser is to remain relevant and even gain back some of it's past importance. FF57 is already a beast performance-wise and i bet that by 59-60 most of the lost functionality will be gained back, if not all.

benbasson commented 6 years ago

I don't dispute that Mozilla are doing the right thing, but I do dispute the timeline. WebExtensions are not mature enough for a huge number of add-ons to be ported, but they are pushing ahead with a fixed deadline for seemingly no real reason.

I am never likely to have one of my add-ons featured in the top 10, or maybe even the top 100, but I do know that approximately 30,000 users of this add-on are going to be waiting for an update for months at best.

Hlsgs commented 6 years ago

@benbasson agreed on this aswell. Considering the state of the API pushing back a couple of releases would have made alot of sense. Regardless, I was just ranting about the tons of highly malicious comments i've been reading about the purported suicide of Mozilla, all laden with threats of moving to either forks of FF or Chrome :)

benbasson commented 6 years ago

In case I didn't make it clear enough elsewhere, I'm currently tracking (and subscribed to updates on):

One or both of these needs to be resolved to my satisfaction in order to reimplement Context Search. I am hoping they will implement the suggestions in those bugs in full, but I am not holding my breath.

I think searching with POST-based engines is (maybe) unlikely to be implemented. If so that puts searching in a new tab or window at risk (at least without some kind of jarring UI behaviour).

EMBBlaster commented 6 years ago

@benbasson, Seems that some features can be achieved. https://github.com/ssborbis/ContextSearch-web-ext/

benbasson commented 6 years ago

Hi - thanks for commenting. The author of that add-on has implemented a function to import each search engine individually, which the users have to set up above and beyond having their search engines installed in Firefox.

I specifically didn't want to do that, because the whole ethos of all my add-ons was keeping things simple - in terms of user experience and also for me to maintain. When the API is finished, I will do what I can and update this ticket.

To be frank, the only reason I'm still here offering to do this is because of the 14 years of loyal usage and friendly feedback I've had from a few tens of thousands of people. This doesn't make me any money, and I no longer use my own add-ons, or Firefox at all. In other words, while the add-on you point to looks excellent, that's about 99% more work than I am ever going to put in.

EMBBlaster commented 6 years ago

Hi - thanks for commenting.

No, I'm thanking you for your work and time devoted to this. Being working with open source code myself, I really appreciate what you did.

The author of that add-on has implemented a function to import each search engine individually, which the users have to set up above and beyond having their search engines installed in Firefox. I specifically didn't want to do that, because the whole ethos of all my add-ons was keeping things simple - in terms of user experience and also for me to maintain. When the API is finished, I will do what I can and update this ticket.

Yes. I agree. Too much work and not really simple. As I didn't know if you was aware of that extension, I leaved that comment in hope it could be of any help for you.

evilpie commented 5 years ago

Hey! I just wanted to let you know that bug 1352598 just landed in Nightly. @smile4ever even already started documenting this on MDN.

Smile4ever commented 5 years ago

@evilpie It didn't land yet in the Nightly builds, I guess we need to have a bit more patience 😀

benbasson commented 5 years ago

Thanks for the message - I am receiving updates directly from Bugzilla on that issue and will continue to monitor.

jtojnar commented 5 years ago

https://github.com/tiansh/simple-context-search looks like a good alternative.

Millichrome commented 5 years ago

@jtojnar Thanks for the link. It's almost a perfect alternative to Basson's context search. One thing I don't like is that it creates a new context menu (although it does support existing search providers out of the box); you still get the "Search [XXX] in Google" context menu. It also doesn't quote the actual text selection. The latter issue seems to be limitation with FF's WebExtension engine.