Last modified: 2009-03-30 00:57:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10234, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8234 - Don't use tables to arrange category page content in columns
Don't use tables to arrange category page content in columns
Status: RESOLVED DUPLICATE of bug 17595
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-12-12 15:49 UTC by Dan Jacobson
Modified: 2009-03-30 00:57 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Dan Jacobson 2006-12-12 15:49:59 UTC
Ho hum. Not to waste my golden keystrokes of months ago, here is
another bug that never made it. "Hope it is still valid".
This is very poor design, forcing needing nodding scrolling in the
browser, that the user cannot disable without editing the page itself:

$ wwwoffle -o|grep 'td>$'
</p><table width="100%"><tr valign="top"><td>

The user is forced to read three columns across the screen, no matter
if the whole table will fit on the screen horizontally or vertically.

If his browser is not tall enough, he is locked into a PDF style view
where he must do several passes up and down, up and down to be able to
read the whole table in alphabetical order.

This violates the whole accessibility principles of HTML. You are
making device dependent expectations whereas users without such large
screens as you are forced into very frustrating up and down, up and
down scrolling to be able to read the table in alphabetical order. He
cannot just keep tapping the spacebar to scroll down like you on your
tall screens.

(True, the user could keep hitting TAB (in firefox) to have the nodding
motion done for him.)

Please use some more device independent method. Yours falls apart upon
tables that are too tall to be viewed on one page.
Comment 1 Rob Church 2006-12-12 16:51:56 UTC
When reporting bugs:

* Please use a descriptive summary
* Please set the version appropriately; if a problem appears on a Wikimedia web
site, select the bleeding-edge
Comment 2 Brion Vibber 2006-12-12 19:40:45 UTC
When CSS3 multicolumn layout is supported by all common browsers, we'll see what
we can do.
Comment 3 Dan Jacobson 2009-03-30 00:57:26 UTC

*** This bug has been marked as a duplicate of bug 17595 ***

Note You need to log in before you can comment on or make changes to this bug.