Related to this topic: it seems like we'd benefit (both on iOS and Android) from moving the "Publish" button in the Talk > Reply UI to the header. For Android users this would mean the button is always visible, and for both iOS and Android it would be a more consistent experience with other Publish/Save actions.
go to existing talk topic tap into text field
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T278588 Mobile talk page improvements | |||
| Resolved | None | T298055 [RELEASE TICKET] Offer Mobile Usability Improvements and Topic Subscriptions at Partner Wikis | |||
| Resolved | Esanders | T295101 Conduct Design Review of Mobile DiscussionTools | |||
| Duplicate | None | T295102 Conduct usability tests with Junior Contributors of mobile DiscussionTools | |||
| Declined | None | T219210 Move the "Publish" button in mobile the Talk > Reply UI to the header |
Event Timeline
Comment Actions
@matmarex The screenshot shows MobileFrontend’s own new topic tool, but the issue is the same with DiscussionTools’ New Topic Tool (and Reply Tool): the button is at the bottom, so if I typed more than a few words, I have to scroll for the button. Is there a separate task for DiscussionTools?
Comment Actions
I'm not sure if it would make sense for DiscussionTools, since we don't have a sticky header there. I don't think we have a task for this in DiscussionTools. If you think that's worth proposing, feel free to file one.
Comment Actions
Ah, good point. Then probably the current solution is the best possible in DiscussionTools, considering that the user needs to see as much of the comment being drafted throughout the drafting, but needs to find the post button only once. If there’s no sticky header already, don’t introduce one.
And what about this task? It’s stalled on T278590, but that task was closed by @ppelberg without making a decision on this task (or on T116686).
Comment Actions
I'm not sure why it remained open for now while other tasks were closed, but I think our plan is to deploy mobile reply and new topic tool everywhere, and then at some point later delete the feature in MobileFrontend and close any remaining tasks related to it.
Comment Actions
I think we can close this, like we did with other issues about the current mobile interface for talk pages (T278590).