| Nikerabbit | |
| Sep 20 2016, 10:08 AM |
| F31856714: Screen Shot 2020-06-06 at 1.57.31 PM.png | |
| Jun 6 2020, 9:06 PM |
| F31856699: Screen Shot 2020-06-06 at 1.48.35 PM.png | |
| Jun 6 2020, 9:06 PM |
As a follow-up to T102922: Let mobile users reach a functioning Special:Translate without clicks, Special:Translate now works on mobile site, but that does not mean it is works well for mobile users. Two things from the previous ticket:
In addition some styles are not correctly applied on the mobile site, so those should be fixed too.
See also
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T146134 Improve Special:Translate for mobile devices | |||
| Open | None | T49117 [TUX] Make message list and editor responsive |
Change 310296 had a related patch set uploaded (by Nikerabbit):
TUX: Simplify message search results row
Change 311945 had a related patch set uploaded (by Nikerabbit):
Editor: fix positioning of textarea action buttons in MobileFrontend & Chrome
Change 312036 had a related patch set uploaded (by Nikerabbit):
Editor: use regular size buttons
Change 312037 had a related patch set uploaded (by Nikerabbit):
Editor: only show shortcut info on large screens
Change 312038 had a related patch set uploaded (by Nikerabbit):
Editor: do not use grid for caret spacing
Change 312039 had a related patch set uploaded (by Nikerabbit):
Editor: Make the insertables more touch friendly
Change 312040 had a related patch set uploaded (by Nikerabbit):
MessageTable: Do not float the action bar on small screens.
Change 312041 had a related patch set uploaded (by Nikerabbit):
MessageTable: make the info column hiding nicer
Change 312037 merged by jenkins-bot:
Editor: only show shortcut info on large screens
Change 312039 merged by jenkins-bot:
Editor: Make the insertables more touch friendly
Change 312040 merged by jenkins-bot:
MessageTable: Do not float the action bar on small screens.
Change 311945 merged by jenkins-bot:
Editor: fix positioning of textarea action buttons in MobileFrontend & Chrome
@Volker_E The things in the task description are still valid. Some cleanups have been done but the major things are still pending.
Hey @Nikerabbit I was just thinking about this today and I was wondering if you could help me with the history of this extension as I'd love to get these to be more accessible on mobile.
Currently languages on MediaWiki.org and other projects that use translate wiki display a language box at the top of the page like so:
Playing with the extension I see that setting $wgPageTranslationLanguageList = 'sidebar-only' puts it in the sidebar like so:
I was wondering why that wasn't the preferred solution here. Can you give me some background?
The reason I ask is that if it's in the sidebar (even if it's repeated at the top of the page or hidden in Vector), it would be trivial (I have a working proof of concept) for us to pick those languages up in Minerva and render them in the language overlay.
(I can open a separate bug or move this comment elsewhere if this is the wrong place to discuss)
In a nutshell:
I think both 3 and 4 could be solvable and desirable to solve.
@Jdlrobson T204076: Consider moving page translation language links to the sidebar has a bunch of more details. If you have any insight how that could be unblocked, potentially in relation with the language selector work, that would be nice.