Perhaps the solution here is to have a "Legacy Browser" skin? You might be
able to find out what browser the user is using from an HTTP parameter and
flip to such a skin automatically.
Nick
Wikimedia developers <wikitech-l(a)Wikipedia.org> writes:
How hard would
it be for us to have and maintain a "lynx-friendly"
html, and serve it to old browsers like this? It seems a shame to
give people something that causes headaches, even if they really
really should upgrade, because maybe they can't upgrade for some
reason (poverty, for example).
Tarquin's made some mock-ups of a more CSS-friendly page layout that
should degrade more gracefully on older browsers; we'll move to that at
some point. Cleaning up the JavaScript to avoid parsing errors in
pre-javascript 1.2 browsers could help as well with the error I
mentioned.