So I am not able to reproduce this 100% of the time, but on both discourse.stonehearth.net and try.discourse.org when attempting to edit a topic’s category, I used to be able to click the box, start typing the category, use the arrow keys, and then type enter or tab. As of this morning (4 AM EST), on 7 of the last 8 attempts to do this, clicking on the category drop down and starting to type resulted in the text appearing in the title field, and not filtering the dropdown. When this occurs, I can no longer see a “text field” in the drop down to type into: [image] Here is what I expect it to look like: [image]

Hey again @eviltrout, based on the my usage (and reviewing the changes you made here): https://github.com/discourse/discourse/commit/5a15c4997cf1a0a34089989e7a2376d730f870e0 I believe that this is fixed… As I am not familiar with the naming scheme used by Discourse, can you confirm if those changes affected the category dropdown?

I am not able to repro this issue here or on try. @jomaxro which browser and operating system you are on?

@techAPJ, Windows 10, Chrome 46. I am getting the error right here on Meta too: [image] and just tried it in Firefox 42: [image]

Hey again @techAPJ, just wanted to follow up that I am continuing to encounter this here on Meta, as well as on the Stonehearth Discourse. Can I provide you with any more details to help find the issue?

Hey Joshua, is your device touch capable? I can repro this on my Surface Pro and iPad and it seems like this behavior is intentional (for touch capable devices) as per this commit by @eviltrout: https://github.com/discourse/discourse/commit/ec02b147b0b26cca869790f560569c44a8871dbb

@techAPJ: Sort of… I have a multi-monitor setup for my system. I have my laptop (non-touch screen), and 2 external 23" monitors (one touch, one not). Let me do some repro attempts with and without the external touch screen connected. Edit: I still cannot consistently reproduce this. I have connected and disconnected my monitor, restarted Chrome each time I change the connection, and still cannot get the typable area at all over at the Stonehearth Discourse. Here on Meta, I did notice the typable area appear during one of my disconnects, but after connecting and disconnecting a second time (where I am currently), I still do not have the typable area. In any case, while I understand this is a very strange edge case, it should not matter whether an externally connected monitor is touch or not as to whether the typable area appears. I can understand an iPad or Surface whose default monitor is touch, but not when my laptop is non-touch and I connect a screen with touch.

[image] Okay so this is where it’s tricky. Pretty much all the iPad regressions with the new composer were due to setting focus() on things in a position: fixed area on iOS 8+. I know the old composer didn’t have the same issues, which is super confusing to me. The best I can reason is that it had a different layout that didn’t make it suffer the same problems? Perhaps we could just remove auto focus on iOS devices rather than all touch? So based on this post by @eviltrout, could the same fix suggested in the quoted thread to simply remove the focus on a fixed area from iOS instead of all touch devices work for this issue as well?

Great, feel free to close this thread.

Attempt to filter category on topic edit results in modifying title

Product Support

codinghorror (Jeff Atwood) November 18, 2015, 11:16pm 2

Can you repro this @techapj?

Topic		Replies	Views
Category dropdown when editing topic title is barely visible Bug	1	992	February 8, 2015
Clicking on category dropdown triggers keyboard on ipad Bug tablet	2	1068	November 9, 2015
New topic composer: Tag box stealing focus from category dropdown Bug	2	770	July 30, 2018
Discourse with a screen reader UX accessibility , screen-reader	137	12111	February 23, 2024
Force users to pick category Product Support composer	26	1231	July 9, 2025

Attempt to filter category on topic edit results in modifying title

Related topics