Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A minor problem with DuckDuckGo search engine:
#1
Dear Admin,

I always personalize DuckDuckGo and Startpage search engines and then add them to web browsers.

During any search I've done with DuckDuckGo in the Cent Browser, often (but not very often) the page which I added its image below is displayed and the "Reload" button no longer works:

http://i68.tinypic.com/245m3wz.jpg

The problem is not very important; but the same personalized engine never causes such a problem in other browsers (both Firefox and Chromium-based). That's why I wanted to let you know.

Regards,
Reply
#2
Seems there is incorrect parameters in address bar.
Have you tried disabling all extensions?
Reply
#3
(09-15-2018, 03:49 PM)CentBrowser Wrote: Seems there is incorrect parameters in address bar.
Have you tried disabling all extensions?

The personalized DuckDuckGo homepage's URL that I have created and used for many years through "Ξ > SETTINGS > Other Settings > (my personal configurations) > Show Bookmarklet and Settings Data"  is as follows:

https://duckduckgo.com/?kl=tr-tr&kad=tr_...ao=-1&kg=p

The personalized DuckDuckGo search engine's URL (for Chromium-based browsers) I have created using the homepage's URL above and added to the browsers for many years is as follows:

https://duckduckgo.com/?q=%s&atb=v36-2b_...ao=-1&kg=p
 
Therefore, there is no difference (incorrect parameters) between this URL and the URL that appears in the address bar in the image I added above (the ones that appear at the beginning of the address bar are search words).
And all the extensions I am currently using are aged like myself; but they are all up to date.  Wink 
There was no such problem in older versions of Cent Browser; it is starting to appear in the new version.

Additional info:

It does not occur after every search: Sometimes it occurs directly when you click the "Enter"  button after typing the search words; sometimes it arises as follows:

When you scroll down the page that shows DuckDuckGo's search results with the scroll bar or the mouse wheel, the problem arises when it comes to the middle of the page. I just realized that the "Reload" button also works on the problem occurred page.
Reply
#4
(09-15-2018, 10:16 PM)taba Wrote: The personalized DuckDuckGo homepage's URL that I have created and used for many years through "Ξ > SETTINGS > Other Settings > (my personal configurations) > Show Bookmarklet and Settings Data"  is as follows:

https://duckduckgo.com/?kl=tr-tr&kad=tr_...ao=-1&kg=p

The personalized DuckDuckGo search engine's URL (for Chromium-based browsers) I have created using the homepage's URL above and added to the browsers for many years is as follows:

https://duckduckgo.com/?q=%s&atb=v36-2b_...ao=-1&kg=p
 
Therefore, there is no difference (incorrect parameters) between this URL and the URL that appears in the address bar in the image I added above (the ones that appear at the beginning of the address bar are search words).
And all the extensions I am currently using are aged like myself; but they are all up to date.  Wink 
There was no such problem in older versions of Cent Browser; it is starting to appear in the new version.

Additional info:

It does not occur after every search: Sometimes it occurs directly when you click the "Enter"  button after typing the search words; sometimes it arises as follows:

When you scroll down the page that shows DuckDuckGo's search results with the scroll bar or the mouse wheel, the problem arises when it comes to the middle of the page. I just realized that the "Reload" button also works on the problem occurred page.

Thanks for clarification.
Have you tried running the browser with safemode.bat?
Reply
#5
(09-17-2018, 04:03 PM)CentBrowser Wrote: Thanks for clarification.
Have you tried running the browser with safemode.bat?

I do not know when and under what conditions this problem arises. If I had known this, I would try to run Cent Browser with safe mode to understand whether I could create the same problem in safe mode.

So, since I cannot artificially create the problem, I always need to use the browser with safe mode and wait until the problem occurs spontaneously. But you'll appreciate that no one wants to do an experiment that is not known how long it will take.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)