# "X new topics" has a gap at the top which can lead to accidental sorting of categories

**URL:** https://meta.discourse.org/t/x-new-topics-has-a-gap-at-the-top-which-can-lead-to-accidental-sorting-of-categories/44227
**Category:** UX
**Created:** [14 במאי,‏ 2016,‏ 5:56am UTC](https://meta.discourse.org/t/x-new-topics-has-a-gap-at-the-top-which-can-lead-to-accidental-sorting-of-categories/44227 "2016-05-14T05:56:57Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Drew\_Warwick](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/drew_warwick/32/80591_2.png) [@Drew\_Warwick](https://meta.discourse.org/u/Drew_Warwick)
#### Post date: [14 במאי,‏ 2016,‏ 5:56am UTC](https://meta.discourse.org/t/x-new-topics-has-a-gap-at-the-top-which-can-lead-to-accidental-sorting-of-categories/44227/1 "2016-05-14T05:56:57Z")

</div>

The “x new topics” (button?) doesn’t cover the whole topic sorting header:

 ![](https://global.discourse-cdn.com/meta/original/4X/9/2/a/92a7cd1c841019ea3455265fa6fcce446c9dc652.png)

If I click on that spot, meaning to click on the “Click to show” button, I accidentally sort the topics by category instead. Here’s a screenshot of what happens after I click where my cursor is in the first screenshot:

 ![](https://global.discourse-cdn.com/meta/original/4X/9/a/6/9a66c13215daecc9a6f2b8616a49e5cdfd987413.png)

This can be slightly annoying when I accidentally misclick and end up sorting by category instead of what I wanted to press. It’d be nice if something was in place to prevent that from happening. Here are some suggestions:

- Extend the height of the “X new topics” button
- Lower the height of the sort buttons to where their Y pixel 0 is in the same place as the “X new topics” Y pixel 0
- Disable sort header while “X new topics” button is displayed
- Disable top portion (above the “X new topics” button) of sort header when “X new topics” is displayed

---

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [19 במאי,‏ 2017,‏ 7:55am UTC](https://meta.discourse.org/t/x-new-topics-has-a-gap-at-the-top-which-can-lead-to-accidental-sorting-of-categories/44227/2 "2017-05-19T07:55:12Z")

</div>

Just ran into this today, looks like it is not yet resolved. Able to repro right here on Meta.

 ![](https://global.discourse-cdn.com/meta/original/3X/c/5/c5f66e0739d1f0e627d3f07e7d45c9b6626738c4.png)

---

<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: [19 במאי,‏ 2017,‏ 8:19am UTC](https://meta.discourse.org/t/x-new-topics-has-a-gap-at-the-top-which-can-lead-to-accidental-sorting-of-categories/44227/3 "2017-05-19T08:19:12Z")

</div>

Sure @neil is cleaning up some mobile stuff, can you add this to your plate too?

---

<div class="post-metadata">

### Author: ![neil](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/neil/32/102150_2.png) [@neil](https://meta.discourse.org/u/neil)
#### Post date: [19 במאי,‏ 2017,‏ 3:07pm UTC](https://meta.discourse.org/t/x-new-topics-has-a-gap-at-the-top-which-can-lead-to-accidental-sorting-of-categories/44227/4 "2017-05-19T15:07:24Z")

</div>

I pushed a fix so that the alert fully covers the column headings.

---

<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: [19 במאי,‏ 2017,‏ 3:07pm UTC](https://meta.discourse.org/t/x-new-topics-has-a-gap-at-the-top-which-can-lead-to-accidental-sorting-of-categories/44227/5 "2017-05-19T15:07:53Z")

</div>