964404 - Use CSS for truncation in buglists instead of doing it server-side

Status: NEW

(Bugzilla :: Query/Bug List, enhancement)

Description

[Asa Dotzler [:asa]]

Can we move the truncation out of the template and let the full HTML hit the page, then use CSS to elide properly? That way it could more easily modifiable and we'd have something that wasn't sending out awfully incomplete HTML to the page so extensions could do more when css wasn't enough.

Comment 1

[Gervase Markham [:gerv]]

For all truncated values, the full value is available in the "title" attribute of the directly-enclosing <span>. So if you are writing an extension or Greasemonkey script, it can look there for the value.

Having spent a few minutes looking into this, I suspect one reason it's not been changed is that it would require significant cross-browser testing.

Also, at the moment, the table is the full width of the page; if you make your browser window too small, you just have to scroll horizontally. If the required behaviour was instead to start truncating the values, one would have to set explicit pixel or percentage widths on each of the columns so that Gecko knew which values to truncate. But doing that means you don't get the "best fit" column sizing that is the default.

If you can find an example of a site which does this with a table of data, I'd love to see how they do it.

Gerv