Add ability to pre-fill the search bar from URL param

[icyflame]

This will enable the addition of MFQP as a custom search engine in Chrome. (with a URL structure something like: https://qp.metakgp.org/?search=%s

I have tested this change, and it works well.

[athityakumar]

A minor change required.

Irrespective of the query in the url param, a / gets added at last - which messes up the search results at times.

Search as URL param :

Search as input to search bar :

Notice the 2nd result missing in case 1. Maybe just the / can be removed from the search_query variable in line 107?

[athityakumar]

@icyflame - I have sent a PR for the same. Have a look! 😄

[icyflame]

I added that search engine to Chrome 56. Then, I searched using the address bar. There was no / that was appended.

Irrespective of the query in the url param, a / gets added at last - which messes up the search results at times.

Who adds the /? If the user manually adds it, that's something that they have chosen to. I don't see the browser adding anything by default even when I manually type out the URL.

[athityakumar]

It gets added by the browser itself (I think. Can't think of any other reason), after the user has typed his search param and pressed the Enter button. For example,

Search param :

Result URL shows a / at the end :

I've added it as a search engine to Google Chrome Version 56.0.2924.87 (64-bit).

[icyflame]

@athityakumar Can you post the search engine entry here? You might have put a / after the %s. If you add the search engine URL as https://localhost:8000/?search=%s the / won't be appended.

In any case, it will be a good idea to remove trailing forward slashes. So, you should change your PR on the other issue to ensure that the last character is a forward slash before slicing it away. 😄

[athityakumar]

Sure, I'll do the required changes on that PR. 😄

[athityakumar]

@icyflame - Um, isn't it the https://localhost:8000/?search=%s?

[icyflame]

Hmm, okay, I guess your browser decided to append the / to the query. Mine doesn't. Weirdly enough, I am on the exact same build of Chrome: Version 56.0.2924.87 (64-bit)

Okay, I will merge that PR and that should update the commit here.

[athityakumar]

Weird o weird. 😕

I've updated the other PR. 😄

[icyflame]

@athityakumar Merged. I have tested with multiple trailing forward slashes, works fine.

[athityakumar]

@icyflame - No more issues from my side, I've approved the PR. Let's wait for reviews of @vivekiitkgp & @amrav before merging this in. 😄

[icyflame]

@vivekiitkgp and @amrav Please review this PR. 🙂

I will merge this PR in a few hours. Thanks!