> If the content really is a table, then it is very hard to imagine how making an entire row into a link could be meaningful.
There are many “skin on a database” type use cases where it can be valuable to present information that’s both tabular (eg summary of columnar information for multiple rows) and navigable (eg to individual row details, edit interface, etc).
There are also many classic (non-web) interfaces with conceptually similar prior art. One that immediately comes to mind is music players, where it’s common to present song list data as tabular, and allow selection of the full row.
These presentations are relatively out of popular usage… but I think that would make them more appealing to a HN audience, which tends to skew heavily in the direction that older UI paradigms were more usable.
There are many “skin on a database” type use cases where it can be valuable to present information that’s both tabular (eg summary of columnar information for multiple rows) and navigable (eg to individual row details, edit interface, etc).
There are also many classic (non-web) interfaces with conceptually similar prior art. One that immediately comes to mind is music players, where it’s common to present song list data as tabular, and allow selection of the full row.
These presentations are relatively out of popular usage… but I think that would make them more appealing to a HN audience, which tends to skew heavily in the direction that older UI paradigms were more usable.