- The display should adapt for mobile screens
|Open||None||T158181 Aim for workflow equivalence for MediaWiki on desktop and mobile web|
|Open||None||T148049 Make APISandbox useable on mobile|
|Declined||matmarex||T209912 BookletLayout is unusable on mobile|
FYI this is intentionally not part of the reading web backlog and probably best addressed by OOjs UI/UI standardisation team since it uses a widget we don't use in the reading web team.
I am removing archived project tags.
Afaik, we do not do that. Why would we? Just because a project is not going to be used in a future, it is a valuable reference at tasks from the past.
It's probably easiest addressed by not absolute position .oo-ui-menuLayout-content & .oo-ui-menuLayout-menu but to put them one atop of another by either float them with menu on top on small screens or reset all positioning to relative (and top/left/bottom/right/display/width).
All the other amendments, like .oo-ui-fieldLayout-align-left make labels go above inputs and set inputs to 100% width are pretty easy then and should probably also go upstream.
But still no time to code this myself.