Page 1 of 1

Qwant search engine broken

Posted: 2022-06-25, 13:35
by carpet
The search engine Qwant.com recently broke in PM. The drop-down menus for choosing the country and time range (labeled "Any freshness") that appear at the top of the search results no longer do anything i.e. you can't click on them. You can see that the cursor doesn't change when hovered. This started a day or two ago. I don't know if anyone besides me uses Qwant but for those who do this is crippling because I have no use for the results tailored for my physical location, which Qwant defaults to and which can no longer be changed except through many clicks in Qwant's settings. I tried Safe Mode and clearing cache, cookies, history, etc.

31.1.0 64 bit, also tried it in 31.0.0
Win 8.1

Re: Qwant search engine broken

Posted: 2022-06-25, 14:07
by vannilla
Please try and include any relevant output from the Toolkit Error Console or the Developer Tools Web Console using the following procedure:
  1. Clear any current output
  2. Navigate or refresh the page in question
  3. Copy and paste Errors or seemingly relevant Warnings into a single [ code ] block.
Doing this right in the OP significantly speeds up finding the solution.

Re: Qwant search engine broken

Posted: 2022-06-25, 15:57
by Sajadi
Edit:

After doing some tests with a fresh portable Pale Moon setup, the page works for me, if i click the banner on top away after making the search i can pick the values of which you said they are broken.

Using here the native user agent

Re: Qwant search engine broken

Posted: 2022-06-26, 10:39
by carpet
Content Security Policy: Couldn’t process unknown directive ‘script-src-elem’
(unknown)
react-i18next:: It seems you are still using the old wait option, you may migrate to the new useSuspense behaviour.
3df38011f8e5041885ab_vendors~app.chunks.js:2:126598
XML Parsing Error: no root element found
Location: https://www.qwant.com/apm/intake/v2/rum/events
Line Number 1, Column 1:
events:1:1
XML Parsing Error: no root element found
Location: https://www.qwant.com/apm/intake/v2/rum/events
Line Number 1, Column 1:
events:1:1
XML Parsing Error: no root element found
Location: https://www.qwant.com/apm/intake/v2/rum/events
Line Number 1, Column 1:
events:1:1
XML Parsing Error: no root element found
Location: https://www.qwant.com/apm/intake/v2/rum/events
Line Number 1, Column 1:
events:1:1

Re: Qwant search engine broken

Posted: 2022-06-26, 10:43
by carpet
Sajadi wrote:
2022-06-25, 15:57
After doing some tests with a fresh portable Pale Moon setup, the page works for me, if i click the banner on top away after making the search i can pick the values of which you said they are broken
- Do you have an explanation then for why (1)it works on one computer but not another and (2) worked on one computer then suddenly stopped working?

- What banner are you talking about? I never had to click any banner; location and time-range options are always right there above the search results.

Re: Qwant search engine broken

Posted: 2022-06-26, 12:04
by gepus
Works for me too.
You don't see the banner because it's probably hidden by an add-blocker.
Please don't be lazy and test next time with a fresh profile before asking for help!

Re: Qwant search engine broken

Posted: 2022-06-26, 19:01
by Blacklab
carpet wrote:What banner are you talking about?
This is the 'VIPrivacy' banner Qwant displays on a clean 'out-of-the-box' test profile of Pale Moon 31.1.0.
Click on the banner's close button and Qwant's drop-down menus will start working... annoying to say the least! :thumbdown:

Quant with banner blocking drop-down menus.jpg
Quant - showing 'VIPrivacy' banner that blocks drop-down menu operation until closed.

As others have noted... on my usual Pale Moon profile I don't see that Qwant banner due to an unidentified filter somewhere in my uBlock Origin's installed filter lists. Disable uBO (or any other Adblockers in use) for that page, refresh page, and the Qwant banner appears.

Re: Qwant search engine broken

Posted: 2022-06-26, 21:34
by Mæstro
Off-topic:
My favourite Qwant glitch is that, if I would search from any Asiatic VPN server, I would get pages where every result was my query string embedded in a Slovenian political report. I do not know whether this has been mended since I forsook Qwant in III 2022.

Re: Qwant search engine broken

Posted: 2022-06-27, 02:31
by van p
The "Any freshness" thing works for me. You mention many clicks in Qwant's settings to get physical location the way you want, but I don't see anything in the settings more than what you can do in that setting at the top of the results page.

Re: Qwant search engine broken

Posted: 2022-06-27, 14:54
by carpet
gepus wrote:
2022-06-26, 12:04

Please don't be lazy and test next time with a fresh profile before asking for help!
What is the difference between a fresh profile and safe mode? I thought the whole point of safe mode was to run a clean unaltered version. If it doesn't do that when what exactly is Safe Mode used for?

Re: Qwant search engine broken

Posted: 2022-06-27, 14:55
by carpet
Blacklab wrote:
2022-06-26, 19:01
Disable uBO (or any other Adblockers in use) for that page, refresh page, and the Qwant banner appears.
My original post makes it clear I tried Safe Mode i.e. no extensions.

Re: Qwant search engine broken

Posted: 2022-06-27, 15:03
by carpet
Edit: solved, see post below

Re: Qwant search engine broken

Posted: 2022-06-27, 15:19
by carpet
Blacklab wrote:
2022-06-26, 19:01
This is the 'VIPrivacy' banner Qwant displays on a clean 'out-of-the-box' test profile of Pale Moon 31.1.0.
Click on the banner's close button and Qwant's drop-down menus will start working... annoying to say the least! :thumbdown:
*This* is the solution! Wow that's horrifically stupid site design. It explains why Safe Mode, and turning off uBlock Origin in regular mode, didn't make any difference, because I hadn't closed the banner, which I'd never have thought of trying. I have troublshot hundreds of sites using Safe Mode or turning off UBO and found many many times where UBO was the problem (i.e. needed tweaking) but this is the first time where the problem was some random secret click which is the way the site was designed that had nothing to do with UBO.