4149: Improve back navigation from the regions page

[bahaaTuffaha]

Short Description

Add a visible "Back to content" action on the region selection page (mobile only).

This would provide users with a clear recovery path when they unintentionally open the region selection flow and help them return to the page they were previously reading.

Proposed Changes

• Created new component just for BackToContentButton.
• window.history.state?.idx reads React Router's current position in the browser history stack.
• edge-case: If you changed the language while at region page the last history page becomes the language change so to ignore this page: we save an entryIndex and subtract it from the history index so we remove any history added while we are still on the same page.
• Created a small test for BackToContentButton.
• While running jest tests on VsCode i encountered some weird issues on the IDE but it's passing the test on cli's yarn test (It assumes one Jest at the workspace root) so I added jest.virtualFolders to vsCode settings.

Side Effects

N/A

Checklist

• Followed the contributing guidelines and conventions
• Considered accessibility impacts and made the necessary adjustments
• Added or updated unit tests (if applicable)
• Added or updated documentation (if applicable)
• Added a release note for native (if applicable)

Testing

• Go to categories then click on the changeRegion button while testing on small screen.
• Test the back button on large screens.
• Test the back button after language change.
• Test contrast mode.

Resolved Issues

Fixes: #4149

---

[steffenkleinle]

Nice work! Works as expected :)

[steffenkleinle]

@ulyanahoy-cloud is Back to content/Zurück zum Inhalt necessary or would a simple Go Back/Zurück be enough? That would save us another translation :)

[bahaaTuffaha]

@steffenkleinle I noticed that I need to run yarn ts:check sometimes to get the new translations working. did we change something in that regard ?

[steffenkleinle]

@steffenkleinle I noticed that I need to run yarn ts:check sometimes to get the new translations working. did we change something in that regard ?

I think it is always necessary due to the switch to esm in #2404

[bahaaTuffaha]

@steffenkleinle I noticed that I need to run yarn ts:check sometimes to get the new translations working. did we change something in that regard ?

I think it is always necessary due to the switch to esm in #2404

How about we run it once after a yarn install or before yarn start?

[steffenkleinle]

@steffenkleinle I noticed that I need to run yarn ts:check sometimes to get the new translations working. did we change something in that regard ?

I think it is always necessary due to the switch to esm in #2404

How about we run it once after a yarn install or before yarn start?

We could do that, but I think it would not fix your problem. You still need to run it manually after adjusting the translations.

[lunars97]

@steffenkleinle I noticed that I need to run yarn ts:check sometimes to get the new translations working. did we change something in that regard ?

I think it is always necessary due to the switch to esm in #2404

How about we run it once after a yarn install or before yarn start?

We could do that, but I think it would not fix your problem. You still need to run it manually after adjusting the translations.

@andrew8er mentioned it before here #4093 (comment) and he said that he will implement this step as well in #4166 if I understood correctly

[andrew8er]

@andrew8er mentioned it before here #4093 (comment) and he said that he will implement this step as well in #4166 if I understood correctly

I'll see how I can implement that. What needs to be run for the translations?

[bahaaTuffaha]

@andrew8er mentioned it before here #4093 (comment) and he said that he will implement this step as well in #4166 if I understood correctly

I'll see how I can implement that. What needs to be run for the translations?

yarn ts:check