LYNX-DEV table idea

[Bela Lubkin]

Curious how well this would work...

Suppose Lynx kept track of column widths during table rendering, and
rendered each new row with each column at least as wide as it was in any
previous row.

The first few rows would look weird, but maybe the overall effect would
be better than the current situation.

This doesn't require a parser rewrite to evaluate the whole table before
starting to render it, so it ought to be somewhat easier to implement
than a "perfect" implementation.

Possible extension: store the computed widths in Lynx's internal
representation of the table; so if it's redisplayed, all rows use the
computed widths.

This still implies a need for horizontal scrolling, but might be fairly
useful even without it.

>Bela<
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;