Author: davidrichfield
Description:
See https://en.m.wikipedia.org/wiki/Template:HeatTable - it works OK on new Android versions, but not on mobile Wikipedia view on desktop browsers or some other mobile devices.
Version: unspecified
Severity: normal
Thanks for taking the time to report this!
(In reply to comment #0)
See https://en.m.wikipedia.org/wiki/Template:HeatTable - it works OK on new
Android versions, but not on mobile Wikipedia view on desktop browsers or
some other mobile devices.
Could you give an example on browsers and screen resolutions that you tested this with? And what does "render very badly" and "not OK" mean? :)
I wonder if you see the same issue as bug 36936.
davidrichfield wrote:
Could you give an example on browsers and screen resolutions that you tested
this with? And what does "render very badly" and "not OK" mean? :)
Windows 7:
The example table, on en.m.wikipedia renders acceptably on Internet Explorer version 8.0 at all resolutions that allow the table to fit into the screen. If the screen size is too small for the table, the table is cropped, with no scrollbar.
On Mozilla 21.0 and on Chrome 29.0.1547.57, only the first two rows render, unless the screen size is smaller than the width of the table: then a scrollbar appears, but only the header row is displayed.
Will check under Linux in a moment - need to reboot my work-laptop under Linux.
I wonder if you see the same issue as bug 36936.
It seems to be a different issue.
davidrichfield wrote:
It renders properly on elinks 0.12pre5 and lynx 2.8.8dev.9 on Ubuntu - both of them scroll the table when the screen size is too small.
Chromium 28 and Firefox 23 on Ubuntu show exactly the same behaviour that I saw on Windows. (note: to be accurate, they render the first two rows properly (header row and first row of data) and show a bit of the third row, but mangled)
Konqueror 4.8.5 renders the first three lines of the table, and offers a scrollbar when the screen size gets too small.
This is a long standing bug that sadly we still have no good solution for - tables are a big problem in mobile and a lot of our pages use them in different ways.
Currently our main strategy seems to be working on templates containing tables on a case by case basis but before that happens this [1] will need to be implemented.
[1] https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates