You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two conflicting methods for hit navigation in the article view that can cause the current page in the document to change when the website is reloaded. (when the current url contains only findHit, findHit is removed and replaced by #hit-index e.g. #10. When refreshing, there are no longer wordstart/wordend parameter, and no findHit, the backend will serve the first page (with a hit?).
How it should work:
The url as seen by javascript should always be the combination of wordstart/wordend/#hit-index
The url in the back-end can be either findhit, or wordstart/wordend/#hit-index. It should be converted to the frontend format and redirect.
The frontend paginator should just generate a new wordstart/wordend/#hit-index url.
The text was updated successfully, but these errors were encountered:
There are two conflicting methods for hit navigation in the article view that can cause the current page in the document to change when the website is reloaded. (when the current url contains only findHit, findHit is removed and replaced by #hit-index e.g. #10. When refreshing, there are no longer wordstart/wordend parameter, and no findHit, the backend will serve the first page (with a hit?).
How it should work:
The text was updated successfully, but these errors were encountered: