-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Unify icon design langauge #213
Comments
I'm not a designer and I'm not good at using tools, so it may take a long time to fix them. InfoIf anyone wants to work on icons. Known issues with current icons.
When workingIt can be seen as transparent because of the
Icon post-processingThere is something to work on after modifying the icon. |
Do these icons exist in older versions of Firefox? Maybe it's possible to retrieve them from their source code archives? |
In this repro https://github.com/BPower0036/UserChrome you have most icons used in Firefox in Fluent design; this means that every icon will be the same as in Edge |
Recently, I was adjusting the padding and size of the icon in the remaining time. (Based on |
I can work on this. I've already done a bunch of icons but there's still many more to go. The ones that I've done are not in any particular order and I've also redone some icons that were blurry. See: https://www.figma.com/file/Iyym2tjRVlb7rxTR1Gmvr8/lepton?type=design&node-id=0-1&mode=design (tip: set the zoom to 100% to see how it should look when used) |
@zapSNH Wow. It's 100% set, so it's easy to compare with the blurry icon!! Overall, the icons have been improved, but there are some things that I want to maintain the metaphor for easy recognition. For example, a folder icon. #33 (comment) And It also feels like animation when it's open. I will write some feedback within tomorrow and comment on it!! |
FeedbackCaptured with Zoom 500%.
Please feel free to let me know if you have any ideas that differ from mine. 1. FolderThank you for reflecting my opinion.
2. TabThe difference from the previous one is the tab shape and the filling.
It looks like a new tab in Firefox, so it looks good. This project also supports other tab shape (conneted to toolbar). Maybe there are the next icons.
Consistency is partially sacrificed, but filled icons serve as a emphasize. Compared to the panel of the edge, it is relatively easy to distinguish. It is natural to emphasize the creation of new tab in the menu that appears when you right-click on a new tab button. 3. Bookmark toolbar
4. Clockwise
5. Tablet
It distinguishes the shape of the tab and is consistent with the shape of the phone. 6. Clipboard
If zoom is 100%, the third bar looks small. In other icons, it feels like it looks appropriate.
It appears to be disconnected. 7. Dictionary
I think it will look better if there is a adjustment in the width and the inner space size.
I think I'll look better if it round or empty. 8. Password Field
9. Duplicate window & Select all tabAs you may have felt while making it, the meaning of these three icons is a bit confusing. (from the beginning)
The first one is the tab itself, so you don't have to touch it.
10. Tag11. Gift box
|
I think it's okay to be almost full (In fact, there are few margins of the bookmark toolbar, and it looks better than it is not distinguished)
Thank you, it's separated so I think I can take it and use it if I need it.
It looks good. It's much better than I imagined!! 😍 After solving the #799 bug tomorrow(There is a slight amount to modify), I'm going to apply the icon right away. |
Here's the repo with all the icons optimized: |
I'm happy to be able to close an issue that's been open for two years. |
Is your feature request related to a problem?
The icons in the context menu, as well as the main menu, seem to be taken from different sources, making them look mismatched.
The solution I'd like
Any new icons should follow Proton's design language (or whatever standard you'd prefer).
Additional context
For example, different icons have different stroke thicknesses, as a result of being from different icon sets.
The text was updated successfully, but these errors were encountered: