If the talk page doesn't exist, Minerva redirects automatically to an edit links. For instance, https://m.wikidata.org/w/index.php?title=Talk:Q21510382 redirects to https://m.wikidata.org/w/index.php?title=Talk:Q21510382&redlink=1#/editor/all.
This is a bad user experience since it hides the talkpage header. I suggest to remove this feature.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T308390 Avoid direct link to edit non-existing talk pages in Minerva | |||
| Duplicate | None | T270537 Introduce New Discussion Tool on mobile | |||
| Resolved | • ppelberg | T282258 Design New Topic Tool mobile UX | |||
| Resolved | • ppelberg | T287805 Introduce talk page empty state experiences on mobile | |||
| Resolved | Esanders | T302298 MobileFrontend editor always launches when opening empty talk pages | |||
| Resolved | Esanders | T302307 "Legacy hint" link doesn't work on mobile | |||
| Resolved | • iamjessklein | T305261 Mobile talk page empty state layout displays unexpectedly |
Clicking on that link doesn’t redirect me anywhere. Clicking on the Talk page tab on the item page does (as the link contains action=edit), but it won’t once the New Discussion Tool is introduced on mobile.
Thanks for your answer. Do you know if we could some JS script in the user page (https://m.wikidata.org/wiki/User:PAC2/minerva.js) to avoid this behaviour? Do you have more details about the calendar of the discussion tool?
$(function () { var talk = document.querySelector('.minerva__tab[rel="discussion"]'); if (talk) { talk.href = talk.href.replace('&action=edit&redlink=1', ''); } }());
may work, but I didn’t test it for edge cases.
The mobile Reply Tool and New Topic Tool have just been enabled on a few Wikipedias (the so-called “partner wikis”) on last Wednesday (T282638), so I’d expect its deployment to Wikidata to be in no less than a few months, maybe even more.
No. For example, it’s not deployed in my private wiki. It’s probably not deployed in many other third-party wikis either. It’s one thing if you decline it, but it should not be considered resolved unless DiscussionTools becomes a hard dependency of MobileFrontend (which I very much hope won’t happen, since not all wikis need perfect discussion tools, and some may want to rather have as few extensions as possible).