Some features are temporarily disabled while we perform website maintenance. We'll be back to full capacity shortly.
- Rated 5 out of 5by Jackie, 5 years agoEdit 14-Dec-2018 below -
Just now tried out your Dec 14 update to Context Search WE.
Thanks for adding the highlight feature which shows where search terms are located in search results pages. Searching the web is something we do a lot, so we use this addon more than others.
Here is some feedback which I hope will be helpful.
Issues below are based on using Firefox with bing and google searches -
I - Search results from words inside quotes are not highlighted, ie "web analytics"
I - Only the first page of search results highlight the search term, subsequent pages don't.
I - When a search results page is opened the search words are not highlighted.
Find in Page Features suggested -
F - Add a Findbar (find box) option selectable from Context, Quick, and Toolbar menus. A search term in a web search would be copied to the Findbar so users don't have to manually type it like they have to do with the Firefox Find API (ctrl-f).
F - To independently find search words in-page, words not copied via web search, the findbar should accommodate manual entry of search words in the findbar.
F - Include up / down arrows with the findbar which find previous / next instances of search term. Highlight the current instance of the search term with a distinct / unique color to show where the previous/next search is currently.
F - Display the number of matches on the current page next to the findbar.
F - Some webpages include hidden instances of the search word where you have to click "show more," "see complete description," etc., before you can see those instances. In findbar tweak, there was a flashing circle which became a smaller and smaller circle to become a bullseye on such hidden instances. This alerted users to click "show more," etc, to see a hidden instance.
Alternatively, instead of adding a separate findbar search box, the new features could be integrated with the present search box -
Fa - a "P" could be added to the existing search box so that a Page find would be done on the current page when the P is clicked. Instead of a web search a Find-in-Page search would find successive instances of the search term with each successive click of the P.
Fa - Previous/next arrows could be added to the current search box instead of using a separate findbar.
Fa - Number of matches on Page could be shown next to the current search box
Fa - Bullseye over current instance would work same with current search box as with a new findbar.
These features could be integrated with the current web search bar, but it may be better to use a separate findbar. Unforeseen features you may want to add later might conflict with the current search box. Plus, a separate findbar would limit the complexity of the current web search bar and not cluttter it with findbar options. Don't mean to suggest a separate addon for findbar, just a separate findbox accessible from the existing search menus.
Do you have a webage for donations via paypal or something similar ?
Edit 6-Dec-2018 below -
Dear Developer (Mike ?) - Thanks for responding.
The built in Find API you mentioned leaves a lot to be desired:
# Every time we open a new page we have to reopen the Find-API before we can use it. Find-in-page follows search-the-web like drinking water follows being thirsty. Find-in-page should be an automatic part of find on the web.
# Firefox Find-API doesnt put a flashing highlight or circle over search terms found. You cannot see some in-page instances of the search term that FF Find API "finds."
Just as CSWE is a big improvement over the FF API search box, CSWE could also include a big improvement over the FF Find box.
Something that mimics ctrl-F might not be any better than ctrl-f. But if functionality was added so that CSWE used the web search term for subsequent find-in-page searches that would be a complete search function.
Without in-page search functionality, the rest of the search task is relegated to the slow awkward ctrl-f dinosaur.
The flashing circle and highlight colors previously mentioned made finding search terms in pages much easier in find-bar-tweak than by using the FF Find API.
Still, CSWE is a great addon. Thanks for your prompt reply.
Original Comment below from 5-Dec-018 -
To me, Context Search web-ext (cswe) is better than the built in Firefox web search. I love it and use it a lot.
Was looking for a find-in-page search tool when I discovered cswe. Had hoped cswe included find-in-page functionality; like find-bar tweak had before it vanished.
Adding capability to find instances of the search term in a results page would be even more awesome.
If I remember right, findbar tweak put a flashing circle around the current instance of a search term in the page, highlighted in green, while other instances were high lighted in blue.
Anyway, thanks for this awesome add-on!(edit) 12-15
> I - Search results from words inside quotes are not highlighted, ie "web analytics"
This is mostly fixed now. I haven't done extensive testing but results look good so far. The behavior in 1.9.3 is to look for literal " in the search results, which obviously most engines don't interpret as part of the search term
> I - Only the first page of search results highlight the search term, subsequent pages don't.
This one might get messy but I'm trying a few things.
> I - When a search results page is opened the search words are not highlighted.
Do you mean in the search bar itself on the results page? No, the API I'm using doesn't look in text input fields from what I can tell. Doing so with highlighting colors would require some fancy overlays and a lot of time.
I'm working on a basic find bar. From your suggestions it looks like you want a straight-up replacement for findbar tweak. I can use that as a reference but the webextension API is limited and there are some things that simply can't be done.
> Do you have a webage for donations via paypal or something similar ?
I don't, but you can help development by giving feedback at the github site. I don't receive notifications when comments here are edited, making it difficult to keep a conversation going. I think I have a good idea what you're after though.
I took a quick look at some images of find-bar. Looks similar to the 'find' feature in android chrome - highlights text, provides a nav bar representing the document map with found words, etc. FF has an API available but to keep Chrome compatibility looks like I need SVG overlays and other workarounds. I'll look into it but don't expect anything too soon.
(edit) 12-6 #2
Found a library (mark.js) that does a good lightweight highlighting and integrates with CS pretty well. Already tested on page results with simple highlighting. I might get something set up sooner than I thought.
(edit) 12-6 #3
Basic functionality is in the repo. If you're familiar with sideloading for debugging you can test it out. Otherwise wait for the next release and it will be there.
Looks like FF has a find API that can highlight words in a webpage. Are you looking for something that essentially mimics ctrl-F ?
- Rated 5 out of 5by Firefox user 13617644, 5 years agoI was searching for replacements to "Context Search", "Add to search bar" and "Searchload Options" - and finally found it. Many thanks!
P.S.: Would love an option to clear the search bar after a search(edit)
New option "Remember Search History" is ready for the next release. Unchecking this option prevents search terms from being stored.
- Rated 5 out of 5by GlasWolf, 5 years agoHaving been forced to move on from Context Search I wasn't hopeful that the functionality could be replicated with the new API. Although managing the search engines is now a little clumsier (through no fault of the developer), the extra functionality and improved user interface in this add-on means this surpasses the original. Thanks Mike B - great job.
- Rated 4 out of 5by Judykator, 5 years agoDziała, choć kłopotliwe dodawanie nowych własnych wyszukiwarek. Ale idzie ogarnąć.
hand by options(edit) Using the 'Add Custom Search' widget from the context menu is by far the easiest way to add new search engines to ContextSearch. Is there a reason you're adding engines by hand? If so, how would you suggest making it less cumbersome?
> Works, though cumbersome adding new own search engines. But he is going to embrace.
Which method of adding engines do you find cumbersome? Are you adding new engines via the context menu or by typing them in by hand in Options?
- Rated 5 out of 5by a fox lover, 5 years agoedit: you're suck a great developer, it's really a good thing that the firefox community has someone like you
(edit) thank you a lot for your hard working and your care for user. Whatever coming next, I'm still happy with your extension
 update, about your question: First, thank for your respond. And here's my answers: I feel it can be very easy for everyone, if they can just see the search results in the sidebar, and then continuous with what they're reading, without having to close the result tab or switch back to their tab, especially when you do the search regularly. And screens are getting bigger and wider, so let the sidebar opened won't be a big deal(edit 8-20)
Looks like using the sidebar isn't too viable right now with the API limitations
* no POST capability (no page injection for POST code, sidebar not considered a TAB)
* can't open sidebar from quick menu / toolbar search (only available to context menu searches)
* limited width unless user edits files in profile dir
* sidebar always opens on install for FF pre-62 (minor annoyance)
Maybe in the future when the API is a bit more robust I can look into it again.
The web extensions API is limited in how sidebars can be opened. I can send search results to the sidebar, but I cannot OPEN the sidebar programmatically in some cases. This may effect usability.
(edit) I'm trying it out now. The sidebar width is limited but I've read it can be increased by making changes to userChrome.css . I can add the option to open search results in the sidebar under -- search actions -- without much additional code.
You want to open search results in the sidebar vs in a tab? Could you explain a bit more about how that would be useful to you?
- Rated 5 out of 5by decembre, 5 years agoGood Job!
Its the best alternavie for some other addon i used a lot before.
I appreciate the « search.json.mozlz4 » automatic import (to import our old Search engine and the big configuration options page (which can be saved !)
- Rated 1 out of 5by Carottinger, 5 years agoGute Idee, vieeeeel zu komplex beim Hinzufügen neuer Suchmaschinen (keine Icon-URL - keine Suchmaschine???) - schon mal was von Usability gehört?> Good idea, way too complex when adding new search engines (no icon URL - no search engine ???) - ever heard of usability?
If you feel adding a new engine is complex, I don't think you're doing it correctly. Right-click a search bar on a webpage and choose 'Add Custom Search' from the menu. Click the Add button or Advanced -> Create to tweak the settings.
> (no icon URL - no search engine ???)
Currently, it does require a valid image to add a new search engine. Maybe it should interpret a blank url as using a generic icon instead of preventing the process from completing.
> ever heard of usability?
Yes I have heard of usability. In fact, most users find this add-on to be very easy to use. Maybe you should consider why you seem to be the exception.
- Rated 5 out of 5by Firefox user 13598358, 5 years agoEasy to use, super custom, can be customized according to personal habits, use the necessary extension of Firefox browser.
However, the setting interface is only one language in English. For some users in different countries, there may be certain obstacles to use. Suggestions: Support for dozens of languages around the world, custom download settings, will be the perfect!
By the way, if the right-click menu display position can also be customized (for example, you can choose to display the position under copy and paste), it is even better!
Finally, thanks to the excellent extensions of Firefox that developers bring to us!
Translate comments using translation softwareThe add-on does support internationalization. Right now there are translations for French and German. I'm always looking for contributors to translate into other languages. If anyone wishes to help, visit the support site on github and edit the files in the /src/_locales/en/ directory. (https://github.com/ssborbis/ContextSearch-web-ext/tree/native-app-support/src/_locales/en)
> By the way, if the right-click menu display position can also be customized (for example, you can choose to display the position under copy and paste), it is even better!
There is a setting for positioning the Quick Menu relative to the cursor with customizable pixel offsets. Do you mean moving the "Search for.." menu item higher in the context menu? Unfortunately, that cannot currently be done with the webextensions API
- Rated 4 out of 5by Firefox user 12655166, 5 years agoWhy search working from firefox search, but not from quick search (open main site page)?
Also can edit search engine, but can't save (auto save if is, not working)?(edit) There was an issue with 1.6.3 which prevented adding a custom search engine from the 'simple' menu. That should be fixed in 188.8.131.52.
> Why search working from firefox search, but not from quick search (open main site page)?
Are you unable to open the quick menu? The quick menu and all other content scripts are blocked on addons.mozilla.org by mozilla. If you're on linux, you might need to set ui.context_menus.after_mouseup to true in about:config
> Also can edit search engine, but can't save (auto save if is, not working)?
Are you editing from the search engine manager in ContextSearch options? There should be a Save button below the form when editing a search engine. Is that not working?
- Rated 5 out of 5by Jose Martins, 5 years agoThanks for this update (1.6.2) and its "Old Firefox Style" option. FF post 57 was sorely missing the good old search bar.
Just a couple of things I hope you'll add in future:
- close after search
- empty search bar after search
again, thank you.> - close after search
Ready for 1.6.3
> - empty search bar after search
The current behavior is to display the last search on a per-session basis. The last search should be highlighted, ready to be replaced with the first keystroke. Closing Firefox will clear the last search from the session storage. Adding the option is trivial but I'm not sure it's necessary. Specifically, what issue are you having with the default behavior?
(edit) This was not working properly under linux. Fix ready for 1.6.3