-
-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mobile UX] Eur symbol displayed below the price of the item #6252
Comments
@filipefurtad0 do you know if the position of the currency symbol is tested automatically ? I forgot but for example I think this bug might not appear in pound for example as the currency symbol is located before the amount. |
@RachL I don't know if this is tested automatically, I had a look at some specs but found nothing. In any case, it should not appear in pound - this is what I wanted to show with the pic above... (left side, UK) Maybe I should add some text/green arrows to it, to make it more clear? I updated the description, hope it's clearer now 👍 |
no sorry it's on me @filipefurtad0 on my phone github wasn't showing me the left image 🤦 |
I was able to reproduce this by just changing the configuration to show the currency symbol after the amount (without changing to Euro, that is). Fix is on the way. |
Description
In the shopfront and when using a mobile device, the Eur currency symbol is displayed below the price of the item. This is observed only for:
• mobile devices
• items with prices in EUR
• prices with 4 digits
See pic below.
Expected Behavior
Eur currently symbol should be displayed like this - i.e., after the price:
Actual Behaviour
Eur currently symbol is displayed like this - i.e., below the price:
Steps to Reproduce
Animated Gif/Screenshot
Below, left side - staging-UK - pound currency is correctly displayed. Compare with pic on the right side staging-ES, Eur currency below the price (red arrows):
Workaround
Rotating your device 90°.
Severity
bug-s3: a feature is broken but there is a workaround
Your Environment
Possible Fix
The text was updated successfully, but these errors were encountered: