# Blue preference Save Changes button should be gray initially

**URL:** <https://meta.discourse.org/t/blue-preference-save-changes-button-should-be-gray-initially/254207>\
**Category:** UX\
**Created:** [February 6, 2023, 2:56pm UTC](https://meta.discourse.org/t/blue-preference-save-changes-button-should-be-gray-initially/254207 "2023-02-06T14:56:40Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)\
**Post date:** [February 7, 2023, 9:42am UTC](https://meta.discourse.org/t/blue-preference-save-changes-button-should-be-gray-initially/254207/11 "2023-02-07T09:42:19Z")

</div>

Dimming or greying is fine for me (just to be less visually attention seeking) as long as (and I can’t stress this enough) **they are still clickable** so the user can get feedback of what is missing/not working after a submission attempt.

> [@jidanni](#):
>
> Anyway, so the Save button should not appear at all, if there is nothing changed yet that needs to be saved.

And strong disagree with this. Showing a save button is a clear indication one _can_ change things and save them. And completely having new UI elements pop up isn’t great UX either.

---

_[View the full topic](https://meta.discourse.org/t/blue-preference-save-changes-button-should-be-gray-initially/254207)._