sh0rty 547 Posted January 12 Posted January 12 Why do we have the ugly little icons next to the Logoart when we have the same setting in the regular Menu? Is this intended? I removed it already with CSS in the WebUI, but in the Windows App it's also present. FR: Remove the icons next to the Logoart, since the setting is already present in the context menu. Or is there a good reason for that duplication?
pünktchen 1350 Posted January 12 Posted January 12 Although i agree with you, just do not use an admin user for regular playback and you won't have those icons. 1 2
sh0rty 547 Posted January 13 Author Posted January 13 9 hours ago, pünktchen said: Although i agree with you, just do not use an admin user for regular playback and you won't have those icons. 10 years and I'm still learning something new about it. Thanks for the info. Nevertheless, also for admin users, this makes no sense imo.
Neminem 886 Posted January 13 Posted January 13 Tbh I use those icons when editing things. Its 1 click less than having to open 3 dot menu. 3
ebr 15665 Posted January 13 Posted January 13 It is also more discoverable. This was a feature request (to have these quick-action buttons) that was implemented.
user24 245 Posted March 1 Posted March 1 (edited) I totally agree that the edit icons don't look the best BUT I also use them both very regularly in the web app. So... The icons can easily be hidden with CSS (which I realize the OP has done something similar already): button.btnDetailEdit.btnEditMetadata.secondaryText.flex-shrink-zero.paper-icon-button-light { display: none; } button.btnDetailEdit.btnEditImages.secondaryText.flex-shrink-zero.paper-icon-button-light { display: none; } But, even better still, the icons can be initially hidden and then made to reappear when the cursor hovers over them: button.btnDetailEdit.btnEditMetadata.secondaryText.flex-shrink-zero.paper-icon-button-light { opacity: 0; transition: opacity 0.3s ease; } button.btnDetailEdit.btnEditMetadata.secondaryText.flex-shrink-zero.paper-icon-button-light:hover { opacity: 1; } button.btnDetailEdit.btnEditImages.secondaryText.flex-shrink-zero.paper-icon-button-light { opacity: 0; transition: opacity 0.3s ease; } button.btnDetailEdit.btnEditImages.secondaryText.flex-shrink-zero.paper-icon-button-light:hover { opacity: 1; } I prefer the second option myself - the detail pages look less cluttered, but the shortcuts are still there if needed. Edited March 1 by user24
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now