A discussion was started by Karl_Romanowski about the inability to enter tags on mobile when they are mandatory. joffreyjaffeux clarified that this is not a regression, but rather a feature that has never been implemented on mobile.
Karl_Romanowski argued that ignoring an explicit admin setting to require tags feels like a bug, and awesomerobot agreed that if admins can require tags, then the tag input should exist on mobile.
A secondary issue with the tag field’s z-index covering @mentions was identified by Karl_Romanowski and fixed by awesomerobot.
To address the main issue, sam suggested showing a modal asking for a tag if it is required on a category and the user is on mobile, while awesomerobot proposed simply squeezing the tag dropdown into the mobile composer.
joffreyjaffeux worked on implementing the solution and joffreyjaffeux announced that it should now be working. davidkingham confirmed that the solution is working great.
On mobile, when creating a new topic I don’t see any tag input, optional or required.
On desktop, when selecting a category that requires at least one tag the optional input isn’t updated to say required until the tag input gets keyboard focus.
Ignoring an explicit admin setting definitely feels like a bug. What would you tell community managers when categories that require at least one tag in the settings are all of a sudden flooded with tagless topics?
Right, I think @j.jaffeux was only clarifying that it’s not something that has become broken, we’ve just never had tagging on mobile so the requirement was never implemented there. Definitely agree that if we’re allowing admins to require tags, then the tag input needs to exist on mobile.
I just made an update to fix that z-index issue with mentions, should be live on Meta in a bit.
I do not see how we can solve this cleanly without unconditionally showing the tag control, I guess we could pop up a modal asking for tag if it is required on category and you are on mobile
Right, the simplest thing is to squeeze the tag dropdown in there. Otherwise it feels like we’d be more seriously rethinking how the composer works on mobile (which is fine, but why not start simple).