# 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:** 5

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [February 7, 2023, 5:46am UTC](https://meta.discourse.org/t/blue-preference-save-changes-button-should-be-gray-initially/254207/5 "2023-02-07T05:46:53Z")

</div>

> [@jidanni](#):
>
> In Preferences this button should be gray, up until the time there is something actually to be saved.

I don’t agree with this… Having elements dynamically change state is confusing to end users and distracting.

What are examples in the wild of these kind of UI?

In a previous life we used to “grey out” the Reply button till you were allowed to post, and it was mighty confusing leading to a large amount of support issues. These days you can click it right away and discover what is wrong.

---

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