My preferred solution would be: Open the content in a modal dialog, preferably (with landscape option). Open the content full size within that modal and use overflow scrolling to navigate it when needed. You can't make tables responsive, it's just impossible. And if you have the Excel app on your mobile, it's not responsive either. It's just a huge scrollable surface (with fixed headers, another thing that is near impossible in HTML :( ).
DJ On Thu, Apr 5, 2018 at 2:05 AM, Jon Robson <jdlrob...@gmail.com> wrote: > Showing the navbox (a 1000px table) on a mobile device (320px) is a > difficult problem and not skin specific as Brad quite rightly points out, > but a template problem. > > Minerva shows navboxes on desktop resolutions - you can see for yourself: > https://en.wikipedia.org/wiki/San_Francisco?useskin=minerva (they are at > the bottom of the page). It only hides them on mobile. > > I've added Isarra's Monobook patch to our staging environment so you can > explore how it behaves with real world content on a real device: > http://reading-web-staging.wmflabs.org/wiki/San_Francisco?useskin=monobook > > Here's a screenshot of Navboxes: > https://imgur.com/a/0I3YP > They appear pretty much the same on any skin on a mobile device - because > they are defined in a wiki page template - not in the skin. I'm not sure > how Isarra plans to handle them, but I don't think there are many options > so I think we should assume good faith in whatever she chooses to do. > > The fundamental problem is a lot of our content is designed for desktop > presentation and needs serious thought on how it can be adapted for mobile. > > > On Wed, 4 Apr 2018 at 13:52 Strainu <strain...@gmail.com> wrote: > >> 2018-04-04 23:41 GMT+03:00 Brad Jorsch (Anomie) <bjor...@wikimedia.org>: >> > On Wed, Apr 4, 2018 at 3:18 PM, Strainu <strain...@gmail.com> wrote: >> > >> >> Skipping navboxes is a decision that was taken by the WMF team >> >> responsible for the mobile site (whatever it was called at the time) >> >> and can be solved cleanly only at the skin level, but I don't expect >> >> this to happen as long as it will break the mobile site. >> >> >> >> Your proposal would be the ideal argument for reversing the current >> >> "solution", yes, but realistically, it's not going to happen >> >> throughout the hundreds of wikis that implemented navboxes. >> >> >> > >> > Here we're talking about Isarra's very interesting project to make the >> > Monobook skin responsive, not whatever decisions WMF's mobile teams may >> > have made in the past for their mobile-only skin. She is not obligated to >> > follow their lead just because they led, and I'd recommend she doesn't in >> > this case. >> >> Maybe I wasn't clear, but that's exactly what I meant as well: I'm >> very curious to see how *Mobile MonoBook* handles that particular >> issue. I most certainly hope Isarra *doesn't* follow Minerva's >> (mis)behavior. If the solution is acceptable, perhaps it can then be >> adapted to Minerva. However, I haven't found any navboxes in the demo >> wiki. >> >> Strainu >> >> > >> > Note that's my personal recommendation and not any sort of official WMF >> > position. I likely won't even be involved in the code review for her >> patch. >> > >> > >> > -- >> > Brad Jorsch (Anomie) >> > Senior Software Engineer >> > Wikimedia Foundation >> > _______________________________________________ >> > Wikitech-l mailing list >> > Wikitech-l@lists.wikimedia.org >> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l >> >> _______________________________________________ >> Wikitech-l mailing list >> Wikitech-l@lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
