1864649 - OpenSearch engine fails to install from mapy.cz

Status: RESOLVED WORKSFORME

(Web Compatibility :: Site Reports, defect)

Description

[vladankudlac]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/119.0

Steps to reproduce:

I'm trying to add a search engine for the website https://mapy.cz/ but it fails with Firefox could not install the search engine from: https://mapy.cz/opensearch-mapycz.xml

1. Open the page: view-source:https://mapy.cz/zakladni
2. Find the following line: <link rel="search" type="application/opensearchdescription+xml" title="Mapy.cz" href="/opensearch-mapycz.xml" />
3. Open the link

Actual results:

Firefox opens the page: view-source:https://mapy.cz/opensearch-mapycz.xml?noredirect=1 which doesn't exist.

Firefox adds ?noredirect=1 query part to the opensearchdescription link which breaks the link.

Expected results:

Firefox should open the page: view-source:https://mapy.cz/opensearch-mapycz.xml

Comment 1

[vladankudlac]

Tried Troubleshoot mode: Yes

Comment 2

[Ardelean Oana, Desktop Test Engineering [:oardelean]]

Managed to reproduce this issue on:

• Firefox 119.0.1;
• Firefox 120.0;
• Nightly 121.0a1;

Tested and reproduced on:

• macOS 12;
• Windows 10;
• Ubuntu 22;

Setting the Component to ‘Search’. Please change if there’s a better fit, thank you.
Setting as NEW.

Comment 3

[Mark Banner (:standard8)]

To make the STR slightly clear:

1. Visit https://mapy.cz/
2. Open the address bar and click the green M icon with the plus symbol next to it.

At this stage the search engine should be installed, but instead a message is presented that says Firefox could not install the search engine from: https://mapy.cz/opensearch-mapycz.xml.

Firefox is not adding ?noredirect=1. When I try this, I see there are four visits happening:

• https://en.mapy.cz/opensearch-mapycz.xml -> 302
• https://login.szn.cz/api/v1/autologin?service=mapy&return_url=https%3A%2F%2Fmapy.cz%2Fopensearch-mapycz.xml%3Fnoredirect%3D1 -> 302
• https://mapy.cz/opensearch-mapycz.xml?noredirect=1 -> 302
• https://en.mapy.cz/opensearch-mapycz.xml?noredirect=1 -> 200

This last response seems to be a "not found page" even though it returns 200.

If I try loading https://en.mapy.cz/opensearch-mapycz.xml directly in private mode, then I see:

• https://en.mapy.cz/opensearch-mapycz.xml -> 302
• https://login.szn.cz/api/v1/autologin?service=mapy&return_url=https%3A%2F%2Fmapy.cz%2Fopensearch-mapycz.xml%3Fnoredirect%3D1 -> 302
• https://mapy.cz/opensearch-mapycz.xml?noredirect=1 -> 302
• https://en.mapy.cz/opensearch-mapycz.xml?noredirect=1 -> 302
• https://mapy.cz/opensearch-mapycz.xml -> 302
• https://en.mapy.cz/opensearch-mapycz.xml -> 200

This time it loads successfully.

In both cases the site seems to be trying to go through an interstitial page which I would guess is potentially their cookie handling alert. However, in this case that shouldn't be needed.

Therefore I think we should reach out to them and ask if they can avoid the interstitial, or make it work for this case. :twisniewski would you be able to reach out to them?

I'm going to move this over to Web Compatibility for the time being, as I think it is more a site issue.

Comment 4

[Calin Tanase]

Attachment: image.png

I've checked the website and clicked on the search bar but I'm unable to find the M icon, the page probably received an update. Mark could you confirm, please?

Comment 5

[vladankudlac]

There is still a link to the opensearchdescription in the HTML, but Firefox no longer offers to add this search provider.
<link rel="search" type="application/opensearchdescription+xml" title="Mapy.cz" href="/opensearch-mapycz.xml" />

Comment 6

[Mark Banner (:standard8)]

Attachment: Screenshot 2024-02-23 at 11.45.20.png

The green icon is at the bottom of the address bar. It will only be displayed if you do not already have Mapy.cz installed.

I've retested this and it appears to be working - when I click the button, the search engine gets installed, and the green M is replaced by a red M. I guess they haven't updated their OpenSearch definition since they last rebranded.

So for me, this seems to be fixed now.