-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Bug] Reduce the radius of the rounded corners #3715
Comments
I don't think it makes much sense to compare with Chrome because Chrome is Chrome and Fenix is Fenix. It's totally okay to have different designs. FWIW, I am not a big fan of Material design and I like the current border radius of the Fenix menu. |
Thanks for the reply. The comparison with Chrome was to show another application that uses rounded corners on Android, it is not frequent to see those menus yet. The menu's rounded corner is too large for my taste, compare it with others non menu rounded corners on the same application. For not being a fan of Material Design, the new UI is taking the most annoying visual aspect of it (the corners) and making it big, like children's toy like interfaces. I hope more feedback comes. |
I agree that the current menus look a little sloppy, but didn't have a great reason to open a bug about it previously. I think that this makes sense from a platform integration perspective. |
@AmyYLee please review and close if border radii are as designed. |
@sblatz Can you confirm if the boarder radius is 8pt? if it is, please leave it as such as this is the same radius as our tab cards. We should keep the radius consistent throughout the app. Thanks. |
The radius was not 8dp. Updating now |
Updated the menu corner radius, closing this |
Thanks everyone involved, with this fixed, adding my next UI related issue |
Steps to reproduce
Open any menu inside the application, the rounded corners of them are too big. Compare the following Chrome and Firefox Preview screenshots from the same device:
Expected behavior
Relatively native looking controls, specially menus rounded corners within Material Design recommendations. There are too many rounded corners, not my personal taste, but the menu ones are too big.
Actual behavior
Menu rounded corners are too big in comparison with other modern Android applications.
Device information
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: