# I dislike the new mobile topic header behavior in 2.2.0.beta5

**URL:** https://meta.discourse.org/t/i-dislike-the-new-mobile-topic-header-behavior-in-2-2-0-beta5/103135
**Category:** UX
**Created:** [30.Ноябрь.2018 03:15:49 UTC](https://meta.discourse.org/t/i-dislike-the-new-mobile-topic-header-behavior-in-2-2-0-beta5/103135 "2018-11-30T03:15:49Z")
**Posts on this page:** 1
**Showing post:** 97

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [16.Декабрь.2018 01:06:37 UTC](https://meta.discourse.org/t/i-dislike-the-new-mobile-topic-header-behavior-in-2-2-0-beta5/103135/97 "2018-12-16T01:06:37Z")

</div>

> [@orenwolf](#):
>
> This is a terrible, terrible way to view engaged users of a product. Folks who disagree with an implementation detail _are not trolls_.

I certainly do not think of it that way. I fully support:

1. A site level customization to revert the behavior for site owners who prefer the old way, and @sam [already built it](https://meta.discourse.org/t/optional-mobile-title-switch-component/104238).

2. The idea that _when a notification comes in_ the header should switch back to the global one, in a just-in-time manner.

That said I do feel quite strongly that the new default is a much better behavior for 95% of the audiences out there … and that’s the entire purpose of defaults.

---

_[View the full topic](https://meta.discourse.org/t/i-dislike-the-new-mobile-topic-header-behavior-in-2-2-0-beta5/103135)._
