The discussion revolves around the inconsistent placement of the Dismiss button on mobile devices in Discourse-based sites. OrcaFrost initially noted that the button appears at the bottom of the list on mobile, even in desktop view, which is inconvenient for long lists. JimPas clarified that on desktop, the button appears at the top right for ‘New’ topics and at the bottom right for ‘Unread’ topics. codinghorror explained that the button’s placement depends on the number of topics, with duplication at the top for long lists on desktop. OrcaFrost provided screenshots showing the issue on mobile, with the button at the bottom despite a relatively small number of topics. codinghorror confirmed the inconsistency on mobile and suggested extending the desktop logic to mobile. The issue was resolved by Roman with a fix in a pull request, and codinghorror confirmed the fix, noting that the Dismiss button now appears at the top of long lists on mobile, improving usability.
Just checked myself.
For New the Dismiss button shows up at the upper right.
For Unread the Dismiss button shows up at the bottom right after the message that reads “There are no more unread topics. Browse all categories or view latest topics”.
Turns out the button is located at the bottom for the browser, which defeats the purpose if there’re hundreds on the list. Is it possible to bring it on the top?
Oh yes, sorry, I was referring to desktop only. There might be an inconsistency on mobile.
Here’s a site with 53 new topics, note placement of dismiss at top and bottom, the dismiss button is duplicated at the top when there are a lot of topics.
I have 8 new topics here on meta, and in that case, the dismiss button is only presented at the bottom .. exactly as I said it would be. Same logic for the Unread tab.
Could be we need to extend this logic to mobile, though. @eviltrout this might be an easy one, can you assign for next week?
Confirmed, I see Dismiss at the top of long lists of Unread and New on mobile right now, as well as within categories. Thanks for bringing this up @OrcaFrost – I was aware of this inconsistency and meant to flag this a while back as an issue … we appreciate the reminder!