stop working on firefox 47 beta Noté 5 sur 5 étoiles

This is by far, the most comprehensive search add-on for Firefox!
many thanks for all the creative work!
it would be great if you could fix the Firefox 47 verification issue.

Cet utilisateur a 2 revues précédentes sur ce module.

Amazing FFox addon... Bestof! Noté 5 sur 5 étoiles

This is a VERY well thought out addon and is incredible. Don't let the simple title of "Fastest Search" fool you... it does a LOT more and it's worth watching his (VERY well done) youtube video to explain how to use the features.

Thank you very much for your work on this and I am already using it like crazy.

Most powerful Search addon Noté 5 sur 5 étoiles

The fastestsearch addon makes browsing with firefox extremely powerful and productive - especially if you become acquainted with help/videos provided by the developer and then tweak the many settings to make the tool work the way you work! I would be lost without it.....

To me one of the best add ons ever. Noté 5 sur 5 étoiles

You are my Hero! Thank you so much per taking the effort to update your add-ons again.
Unfortunately Mozilla FF team constantly causes add-ons to break which requires lots of work to repair so... are you thinking to create a new version for Chrome by chance? I switch there when I'm having problems here, so to have your add-on on Chrome too would be quite handy.

My pleasure! I must admit that the recent decisions by Mozilla do not sit well with me (and a lot of addon authors). With the webextensions switch, I suspect FS will suffer 20% loss of features and I'll have to rewrite a lot of code. So yes, very likely I'll port FS to Chrome and make that the priority from now on. Frankly I myself use only Chrome for work stuff. I only browse with FF because of FS (everything else I want have Chrome equivalence already). I'll likely still keep FS working for FF, however, and thanks for sticking with FS in either browser!

Fearing the day it stops working Noté 5 sur 5 étoiles

The first thing I install. At work I have to keep downloading portable firefox everytime, but I do so, beacause of FastestSearch.

I configured it to my wishes, including many handy search engines and backed it all up, so all I have to do after reinstall is import the settings.

On my Linux machine, FS sometimes doesn't come up spontaneously, but a disable and reenable makes it work again.

I fear the day FS stops working, because Firefox will no longer support it. I hope you will work it out together.

Cette critique est pour une version précédente du module (3.31.1-signed). 

The 3.38 is just released. I will most likely keep it working in FF, but my priority might be switching to providing FS for Chrome. Either way, I myself use FS every day so rest assured it will be working in one of the browsers. In Chrome some of the features would have to be truncated because Chrome does not allow the power - however, same will happen to FF soon, due to their switch to webextensions. So won't be too much loss.

Must Have! Noté 4 sur 5 étoiles

Seriously why not have the options in a more convenient place? I had no problems finding them however someone who is amateurish might have some problems getting to them cause they're kind of buried and for no good reason...just because I guess. Put options in an easier place, doing so much just to reach something that other developers all have in the add-on's page is a little ridiculous.

Other than that I would dare say its one of the best add-ons currently available.

Cette critique est pour une version précédente du module (3.31.1-signed). 

I would assume that those who are not as computer literate would read at least the first couple paragraphs of the addon page and notice "To get started ...". The demo video is perfect for those users, and in fact any new users to get familiarized with the myriad of features this addon has.

If you think from my point of view, seriously I've put in so much time into this addon, so much time to cater to user requests to put in ever more options, AND I put in options at a time when Jetpack toolkit itself doesn't have a place to put options (hence a legacy reason) and it's going to be way too much effort to gain nothing - I'm rather happy that I always have quick access to FS options from the toolbar, instead of clicking around multiple times just to load the slow about:addons page to change. And the FS icon is not wasted space (its flashing is useful), so why can't a user spend a few minutes to read and watch the first couple mins of demo video?

If they venture to spend more time to learn all the features/read docs, they'd see that everything was actually planned or has a very good reason.

Must have for investigators Noté 5 sur 5 étoiles

Thank God and of course Mingyi Liu for this Extension!

The "Smart Searchbox" and
"Regular Expression" feature is a gift for all professional surfers!

One problem though is that the red search field sometimes overlays the search hit.

Cette critique est pour une version précédente du module (3.31.1-signed). 

Drag and Drop Noté 5 sur 5 étoiles

When i drag a link and drop it open in foreground tab can i changed to open in background tab

oh wow thanks amazing addon

Cette critique est pour une version précédente du module (3.31.1-signed). 

Right click and drag a link to:
Upper right = open link in a new foreground tab to the right of current tab
Lower right = open link in a new background tab to the right of current tab
Upper left = open link in a new foreground tab to the left of current tab
Lower left = open link in a new background tab to the left of current tab

BTW if you hold down Ctrl key while right click-n-drag you open link in a preview window. This feature's been available forever but I forgot to document it. Just added it to addon page.

like it Noté 5 sur 5 étoiles

Good job

Cette critique est pour une version précédente du module (3.31.1-signed). 

Keyword&Category not support Chinese Noté 4 sur 5 étoiles

Nice add-on,hope Chinese UI.
关键词不支持中文,希望界面可以中文化。

Cette critique est pour une version précédente du module (3.31.1-signed). 

DEACTIVATED in Firefox 43 :( Noté 5 sur 5 étoiles

FF 43 won't let me use Fastest Search because it's not signed!

I managed to activate it by going to about:config and changing "xpinstall.signatures.required" to false. This backdoor won't work with FF44 though.

Cette critique est pour une version précédente du module (3.31.1-signed).  Cet utilisateur a 2 revues précédentes sur ce module.

Yes I know that. I'll have a new version out by then, which should be 3 months later in usual cycles.

Essential addon, but... Noté 5 sur 5 étoiles

I've been using this addon since almost forever, it had almost everything I needed to search inside the bar using shortcuts as well as having the advantage of the instant and configurable popup search box. However, it grew harder to use this addon throughout the past few months due to the signing issues and most importantly the inactivity of the development. I also experienced some slow-down when I hit the search box as well as the weird problem of opening the new search tab left to current tab and not to right to it or to the last tab. I hope the author continues the development of this very essential addon to many of the faithful Firefox users.

Cette critique est pour une version précédente du module (3.31.1-signed). 

For tab opening on left not right, you can use option to change it. Click FS icon, choose Misc. Settings -> Uncheck "Open SSB/search result tabs on right". This is changed because now if you open a search tab and then close it (after finished reading), you'd go back to original tab automatically. It's better than before.

I am developing it, but the new FF changes would mean I have to significantly rewrite almost everything, and cut 20% of features too. It's extremely annoying and time consuming. From a user's standpoint, you wouldn't notice such huge changes are happening in the backend. But rest assured, I myself use this addon every day, and it will live on. If not in FS, it'd be in Chrome - I'm tired of having to change code a lot during FF upgrades. My addon in Chrome only required one time change over so many years.

Fastest Search - Query regarding latest updates Noté 4 sur 5 étoiles

Hi Mingyi,

Fastest Search definitely is a very useful addon. However, is there any reason why the updated version 3.363 is not published in the AMO site? Also, not sure why you are asking users to turn off Addon/Extension signing from FF 41. I believe your response would help put a rest to the doubts in the minds of other like minded users.

Cette critique est pour une version précédente du module (3.31.1-signed). 

A fair request and I'll answer it below as detailed as I can:
1. Why 3.363 is not on AMO?
To be on AMO, you have to pass a lengthy review process. I always did that. But starting from v3.35, the AMO reviewer requested that I remove the eval used in my code that passed the review before after I explained to previous reviewers. I was already starting to work on v3.38 at this time, and it was a big change. However, to get FS back on AMO, I branched the code out, removed that eval and uploaded v3.362, but got rejected again for using innerHTML and another eval in content scripts, both are safe usage and passed previous reviews. The editor decided not to accept my explanations and insisted on me fixing those. It's at this moment I decided that it's NOT worth it to try it on AMO. Every edit I make in the v3.36x branch has to be copied back into v3.38 branch. It's a hassle. More importantly, I was tired of the lengthy and changing review process. That's why I hosted it on my site. For my Google Chrome extension I get to update it myself and get it published right away. AMO takes up to a month and possibly back and forth even on issues that were noted and passed b4.
2. Why I ask users to turn off addon signing in FF41.
When I decided to host FS on my own website, FF did not require signing yet. But later on, FF decided to disable hosting FF addons on external sites. They wanted total control of the ecosphere, and they did it through signing (only those passing AMO reviews get signed). Their initial timeline was that in FF40 they'll warn about an addon not being signed - which means you can still use FS 3.363 by just ignoring the warning; in FF41 they disable the unsigned addon but allow you to override with a about:config option, and this is why I was asking users to use this option to turn off disabling unsigned addon - otherwise FS 3.363 doesn't work; in FF42 and above the about:config option is gone/useless. That's why I said I was working on newer version that will be on AMO again, because they force everyone back. However, later FF pushed back to time line and will disable unsigned in v42 only, and will disallow override in v43 only. So in FF41 it doesn't matter if you use the about:config option or not.
3. When will the new FS version released on AMO?
I'm almost done with FS 3.8, which meets all previous reviewers' comments. But I still need to decide/implement a few things. I'd put FS 3.8 timeline to be out mid Nov to mid Dec, depending on AMO review process length.
4. Why didn't you write about this earlier?
Simple - did you see how much docs I wrote about FS EVERYWHERE? On AMO site, on my own site, inside FS with every '?' along with multiple videos? Did you know many complained "too much doc/info" already? I don't wanna spend more effort on writing a lengthy explanation that people won't read. Since you requested, I wrote it.

Finally - I'm not sure your tone in your initial request is cordial. Trust me, not every addon author is out to get you. We're not trying to hack your system. I put it on my own site NOT to sneak in some vicious code. FS is in plain, uncompressed JS code. Anyone can see in code from signed v3.31 to unsigned v3.363 there's not much change just simple bug fixes. A lot of work on addons are done/required beyond knowledge of common users, that doesn't mean something bad is happening.

And frankly FF recently did some ridiculous decision making, the requiring signing was met with a lot of criticism from addon authors, because this means that I can't even write a private addon for myself, or for my company, which we do have private addons. It's silly. The worse decision they made is to get rid of XUL/XPCOM in a year or so. This would mean a LOT of the powerful addons will lose its power, including at least 20% of FS's most powerful features, and there's NOTHING I can do about that. Needless to say this FF change was met with uproar from addon authors. Frankly I'm not even certain it's worth it for me to keep rewriting to meet the somewhat-changing AMO review rules when FS is gonna be crippled in a year anyhow.

So FF is not always the "good guy" here in addon ecosphere. Those who don't comply with the arbitrary "signing" addon rules are not "bad guy" by default that have something to hide. I'm only reply in detail because yes, like you said, there will be users that'd like to ask about this again. It is, however, annoying to have to be questioned this way.

Noté 5 sur 5 étoiles

An irreplaceable add-on even at the moment, but...
Very slow with e10s enabled. Almost impossible to use. FAYT without search panel not works at all. Please fix it, Mingyi.
UPD. it's too early to say that e10s requires switch to webextension. Now it's not needed and XUL is enabled. It's 1.5 years before mozilla will cut XUL and XPCOM. So if you do not want make addon, it's your right. ok.
UPD2. Mingyi, i specifically writing a new review with the same content, so you can copy/paste your reply to it from the reply to ulf3000.
So, I don't blame you. If removing XUL from FS is really needed to support e10s.

Cette critique est pour une version précédente du module (3.31.1-signed).  Cet utilisateur a 3 revues précédentes sur ce module.

Update 2: I'll see what I can do. I certainly want to use FS myself as much/long as possible.
Update: e10s doesn't require webextension, but you requested fixing the performance issue with FS, which is only fixable by FS using webextension or at least abandon XUL/XPCOM. FF said XUL is out in 12-18 months, but that's irrelevant to my main point: As I said, if FF cuts its best feature, what's the point for me to keep developing for a dead browser? Have you seen the market share drop of FF over the last few years? The only remaining loyal users, do you know why they kept using FF? I'd venture to guess it's because of more powerful/unique addons. Now these addons would either be gone or much less powerful. What do you think would happen to FF's already much dwindled market share? I wanted to make addons and I made a number of them, but Firefox stepped over the line here and forced my hand. It's that simple. Don't blame me for the mistake Firefox made. Read my code in FS and see how you get rid of XUL/XPCOM there without impacting many features. A big rewrite can retain some of them but won't rescue others. It's NOT worth it. I don't want to spend a lot of effort just to keep a half baked version alive.

Old reply: Unfortunately e10s support pretty much requires switching to webextension, which is not even stable itself and worse, doesn't support XUL and XPCOM. FS, despite being a restartless/addon SDK-based addon, utilizes XPCOM API extensively (plus some XUL for UI) due to the deficiency in addon SDK API (even after this many years). To switch FS to webextension will both require serious time commitment from me AND lose a lot of features that won't be possible initially, for years, or even for ever (for some I'm sure).

I don't know what FF developers decided to kill the last remaining advantage of FF over Chrome. But given that I don't understand why they put that pocket thing on everyone's toolbar either, maybe I'm just too old fashioned.

I'll try to rewrite, but if I do rewrite, writing an FS for Chrome and TT2 for Chrome would be my priority because FF's webextension is simply going to be similar to Chrome's but Chrome is a much more stable/consistent system, it's easier to release new versions, and it has a much larger user base now. It'd be a time saver for me while reaching out to more users.

So for now, sorry, please just not enable e10s - it's simply not worth my time to deal with it now when it's not even stable itself.

Noté 5 sur 5 étoiles

Makes my work easier and extremely comfortable. Thanks!

Cette critique est pour une version précédente du module (3.31.1-signed). 

Noté 5 sur 5 étoiles

AMAZIG BUT the search field opens on my second monitor

Cette critique est pour une version précédente du module (3.31.1-signed). 

Thanks & unfortunately that's a Firefox Addon SDK bug: https://bugzilla.mozilla.org/show_bug.cgi?id=955918

wolwerine: I couldn't reply to your review - I suspect it's because you reviewed 3 times in the same thread and I deleted my old reply, and that caused AMO to hit a bug of its own (it kept telling me error when I try to reply). So I'm replying to you here, hopefully you see it - next time use a new review or write email:

Update: e10s doesn't require webextension, but you requested fixing the performance issue with FS, which is only fixable by FS using webextension or at least abandon XUL/XPCOM. FF said XUL is out in 12-18 months, but that's irrelevant to my main point: As I said, if FF cuts its best feature, what's the point for me to keep developing for a dead browser? Have you seen the market share drop of FF over the last few years? The only remaining loyal users, do you know why they kept using FF? I'd venture to guess it's because of more powerful/unique addons. Now these addons would either be gone or much less powerful. What do you think would happen to FF's already much dwindled market share? I wanted to make addons and I made a number of them, but Firefox stepped over the line here and forced my hand. It's that simple. Don't blame me for the mistake Firefox made. Read my code in FS and see how you get rid of XUL/XPCOM there without impacting many features. A big rewrite can retain some of them but won't rescue others. It's NOT worth it. I don't want to spend a lot of effort just to keep a half baked version alive.

Old reply: Unfortunately e10s support pretty much requires switching to webextension, which is not even stable itself and worse, doesn't support XUL and XPCOM. FS, despite being a restartless/addon SDK-based addon, utilizes XPCOM API extensively (plus some XUL for UI) due to the deficiency in addon SDK API (even after this many years). To switch FS to webextension will both require serious time commitment from me AND lose a lot of features that won't be possible initially, for years, or even for ever (for some I'm sure).

I don't know what FF developers decided to kill the last remaining advantage of FF over Chrome. But given that I don't understand why they put that pocket thing on everyone's toolbar either, maybe I'm just too old fashioned.

I'll try to rewrite, but if I do rewrite, writing an FS for Chrome and TT2 for Chrome would be my priority because FF's webextension is simply going to be similar to Chrome's but Chrome is a much more stable/consistent system, it's easier to release new versions, and it has a much larger user base now. It'd be a time saver for me while reaching out to more users.

So for now, sorry, please just not enable e10s - it's simply not worth my time to deal with it now when it's not even stable itself.

Noté 4 sur 5 étoiles

Don't work on Firefox 40.* :( ... Please, fix it
***My apologies for the previous 1 star due to an error ... I corrected my review. It is a very good extension for this I made my request. But now, the problem with FF 40. * is solved and I hope the same is true for the misunderstanding with the developer.

Cette critique est pour une version précédente du module (3.31.1-signed). 

Update: Thanks & glad to hear it's working now.

Noté 5 sur 5 étoiles

Excellent addon - A must have.

v3.363 is required for FF40+

My only gripe is the use of SuperFish for the shop assistant feature. SuperFish has a very bad reputation and is even blocked by many Internet security products. Fortunately it can be disabled so I give Fastest Search full bars!

Cette critique est pour une version précédente du module (3.31.1-signed). 

Thanks! I must note that Superfish used for Shopping Assistant is MUCH MUCH different than the certificate thing that gave it a bad name in security community. If this compromises my users' security I wouldn't have put it in FS.

can we have Android version? Noté 5 sur 5 étoiles

Great job, can we have Android version?

Cette critique est pour une version précédente du module (3.31.1-signed). 

I do want to be able to search faster on Android too, so I'll investigate. No promise yet. Regardless definitely a lot of features would be cut off as Android FF won't support it.

Noté 5 sur 5 étoiles

By far one of the best addons I’ve ever seen!
Especially drive directions h 2h shortcuts are just superb
Keep on great work.... hope to see future development.

Michael

Cette critique est pour une version précédente du module (3.31.1-signed).