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
Hosted portals have their own translation dropdown. That works when you just arrive on a page, but with history push the HP menu dropdown will not be updated. And so it will point to a different page.
E.g. user arrive at collection/search. The HP knows that the spanish version should go to /es/collection/search and that is hardcoded at build time into the dropdown content.
But when we then do a history push to a collection detail page like collection/123 then the dropdown will still point to /es/collection/search.
Ideas:
lib emit events that a hp script can pick up on and update the dropdown.
The text was updated successfully, but these errors were encountered:
Hosted portals have their own translation dropdown. That works when you just arrive on a page, but with history push the HP menu dropdown will not be updated. And so it will point to a different page.
E.g. user arrive at
collection/search
. The HP knows that the spanish version should go to/es/collection/search
and that is hardcoded at build time into the dropdown content.But when we then do a history push to a collection detail page like
collection/123
then the dropdown will still point to/es/collection/search
.Ideas:
lib emit events that a hp script can pick up on and update the dropdown.
The text was updated successfully, but these errors were encountered: