Steps to reproduce:
Expected results:
Corresponding page is loaded.
Actual results:
A 404 page is loaded.
Notes/Issues:

Arg, shoot, I forgot about this. It’s because we use link to rather than href. I can fix this easily. My bad. 😓
On 6 Oct 2017, at 09:53, ValentinaPC notifications@github.com wrote:
Steps to reproduce:
Load https://addons.mozilla.org/en-US/android/ on your device
Go to "More..." and click "Dictionaries and Language Packs"
Expected results:
Corresponding page is loaded.Actual results:
A 404 page is loaded.Notes/Issues:
I saw this on desktop too, but thought that it is not implemented, and will not be an issue, if we are still using old AMO pages for production, but on device, this is an issue that users can encounter.
Verified in AMO-prod FF58(Android 7.2.1).
Screenshot for this issue:—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Note the desktop and mobile pages are the same as long as seen on this new site now. The only different between device and browser is the viewport/css rules applied. Everything else should be the same between desktop/mobile now. I guess the addons returned are different too but that’s because of a different clientApp 😀
Note the desktop and mobile pages are the same as long as seen on this new site now. The only different between device and browser is the viewport/css rules applied. Everything else should be the same between desktop/mobile now.
I thought that the link will work only after issue https://github.com/mozilla/addons-frontend/issues/2777 will be fixed. That's my bad. :(
Is there a chance to fix this for this push? Thanks!
Hmm, I have the actual page ready and we could pick it, so yes.
Just FYI this won't be visible on a direct page load until #3438 is closed, but you can navigate here from another page.
Verified as fixed on AMO-dev FF56(Win 7, Android 7.2.1).
Postfix screenshot:

