It says first press Search at the top of the screen,
Well I did, and the keyboard pops up, and now it’s not clear where I am inputting words into.
סיכום מבוסס בינה מלאכותית
The discussion revolves around a confusing topic template on mobile, particularly in the Product Support category of Meta. jidanni reports that pressing ‘Search’ at the top opens the keyboard but obscures the composer, leading to a UX issue where input goes to the hidden search field. MarcP explains the template’s purpose and suggests it should be removed. Don clarifies that navigating to search shifts focus to the search bar, hiding the composer and causing confusion. Jonathan5 notes the lack of a visible search icon and suggests a dismissible panel. Jagster states the issue is not about Discourse’s UX but Meta’s template, and HAWK moves the topic to #site-feedback for further discussion.
Well I did, and the keyboard pops up, and now it’s not clear where I am inputting words into.
3 לייקים
This shows for everyone opening a new topic in Support, it’s called a Topic template. You are supposed to remove it and then compose your post.
4 לייקים
Yes, but following its instructions leads to a UX disaster at least on a cell phone.
So there is competition between the topic creation buffer and the search buffer. They can’t coexist.
3 לייקים
Hello,
What is happening here is when you clicking search it navigate you to the /search page and the focus is automatically goes to the search input this is why the keyboard shows up but the opened composer hide the whole page so you can’t realize what is the actual page where you are and seems nothing happened. But when you start typing it will put the text to the search input field.
I think it would be nice if the composer minimized automatically on mobile (Android) when it is navigated to an other page. 
5 לייקים
Okay things we type are going to the search box which is hidden… 100% UX disaster!
I don’t either, which means there is no magnifying glass icon “at the top right” when that text is displayed. I’ve never liked that template. Some sort of dismissible panel might be better.
I didn’t like that template either. And that’s why I changed it. As supposed.
So this topic isn’t UX of Discourse anymore, if has ever been. It is topic of UX of Meta.
3 לייקים
You’re right. It belongs in Contribute > Site feedback really. They’ve had topic templates since at least 2016 (Using topic templates for categories) but I think the one in question here was introduced within the last couple of years.
“Can’t blame me” for being unable to tell if it was a
- local feature, as it turns out to be, or
- the way the newest version of Discourse looks.
Nope, without full details, like
available to the end user, it’s all a guess.
I have moved this to site-feedback because it’s specific to Meta and the template we use here.
לייק 1