addons
addons copied to clipboard
mozilla
Extensions list link on /firefox/ homepage is incorrect after going back when using Android
Describe the problem and steps to reproduce it:
- Accessing the extension store, on the phone.
- Access See more recommended extensions, from the category of recommended extensions.
- After the first access, the address can be entered, we go back and access the same address again, it no longer works and an error appears.
(Please include as many details as possible.)
What happened?
On the mobile extensions site, the recommended extensions page does not open correctly.
What did you expect to happen?
The page must load correctly, every time.
Anything else we should know?
(Please include a link to the page, screenshots and any relevant files.) https://addons.mozilla.org/en-US/firefox/en-US/android/search/?promoted=recommended&sort=random&type=extension
And accessing this link doesn't work.
https://github.com/mozilla/addons/assets/114283947/c68a424d-d216-4ee6-8fd5-64a5f84702c4
┆Issue is synchronized with this Jira Task
Reworded STR:
- Go to https://addons.mozilla.org/en-US/firefox/ with Firefox for Android (the
/firefox/part of the URL matters, as well as using Firefox for Android - this is not the "right" homepage for Android!) - Tap "See more recommended extensions". You land on https://addons.mozilla.org/en-US/firefox/search/?promoted=recommended&sort=random&type=extension which loads fine (you are still on a Firefox page while using an Android device, though)
- Go back using browser button
- Tap "See more recommended extensions" again
Expected Results:
- You land on https://addons.mozilla.org/en-US/firefox/search/?promoted=recommended&sort=random&type=extension again
Actual Results:
- You land on https://addons.mozilla.org/en-US/firefox/en-US/android/search/?promoted=recommended&sort=random&type=extension which doesn't work (it has both
/firefox/and/android/in the URL)
@diox @willdurand Can this error be resolved? I think it would deserve a fix.
Every issue that is still opened deserves a fix, but we don't have capacity to fix everything. I'll gladly review a patch for this if someone wants to give it a try.
