Some views use a .ui.basic.button and some views use .ui.teal.button or .ui.primary.button. The issue with using a primary button color for secondary actions is that it dilutes other, actually important buttons like form save buttons. The UX around buttons should be that secondary actions are not primary colored.
I think the correct pattern here is to use .ui.button instead for all of these inputs. This mimics listing views, where icon buttons are not .ui.basic or .ui.primary.button:
And would look like this:
[x] Replace button styles anywhere we use the data-clipboard attributes and clipboard pattern
[x] Replace the icon style with fad -> fas, as we use solid icons on listing menus
Some views use a
.ui.basic.buttonand some views use.ui.teal.buttonor.ui.primary.button. The issue with using a primary button color for secondary actions is that it dilutes other, actually important buttons like form save buttons. The UX around buttons should be that secondary actions are not primary colored.I think the correct pattern here is to use
.ui.buttoninstead for all of these inputs. This mimics listing views, where icon buttons are not.ui.basicor.ui.primary.button:And would look like this:
fad -> fas, as we use solid icons on listing menus