ng.html - Check For Existing Glosses Results

Tested on https://glossing.rerum.io/ng.html#https://store.rerum.io/v1/id/614362c3e74876243131a4e0

Duplicate looking results appear, but each item has a unique ng.html# link.


Upon clicking one of them, the # in the address bar becomes the hashed id instead of the URI. This is not recognized on any page. You will get a 'hash is not a URI' toast error if you go to a page without a #URI.

The link away never occurs. The links do not result in a redirect, but do change the #id on the ng.html page itself. Forcing the page to load with hash id results in the 'hash is not a URI' toast.

Start with ng.html and reproduce the existing-gloss results using the URL in the report. Trace how each result link is built and handled when clicked. Done means selecting a result navigates to a recognized URI rather than replacing the page hash with an unrecognized id or showing the “hash is not a URI” toast.

Written by the indexing model from the issue text.