Attachment:
[ticket.JPG](http://issues.piwik.org/attachments/453/ticket.JPG)

Matt’s plan is to use jquery truncate. See ticket #159.

#159 didn't fix this issue, so I'm re-opening for investigation, i.e., is it possible to truncate to the visible width of the table cell (instead of the fixed string length truncation (which results in the first 30 characters + '...')?

Anthon,
I agree, your suggestion is how things should work. For example, GA tables have the label end of string disappear when the browser window is set to lower width. I think it is using overflow:hidden;. We would then deprecate jquery truncate.

I'm leaving this in the 0.7 milestone as this bears more investigation and cross-browser testing.

For example, Firefox doesn't natively support overflow:hidden in a table unless the table layout has fixed-width columns. As I understand it, this is "by design", due to the way the table reflow algorithm is implemented.

I tested 3 other jquery plugins that truncate text to the container width, but none overcame the above table limitation. These were tested outside of Piwik using a simple multi-column table (auto layout).

Note: Piwik has an additional hurdle: the data table has not been added/rendered to the DOM yet when the cosmetics are applied, so the computed width is 0.

Interesting. Did you try the case where inside the TD label, there is a DIV containing the label, that has the css overflow attribute?

Firefox ignores the overflow:hidden and auto-expands the table so that it's wider than the css width:450px that I set on the table. This is the auto-layout/reflow logic at work.

Ditto for IE8.

The jquery.textoverflow plugin is interesting, but it requires that the table already be rendered, so there's a flash as it restyles the table. Sort of works with FF (width calculation is off when table has borders); doesn't work at all in IE8.

I see... the way piwik builds table is an issue. we should probably instead have the ajax return pure json, and the JS do the full rendering. This would be much cleaner and easier to maintain, but it is not trivial to change all the code to work this way.

What would be great would be to have the label hidden just when the second column starts, and have possibility to double click to select (and eg. copy) the full label (including the hidden part). Again, I don't know if this is possible...

For example, Firefox doesn't natively support overflow:hidden in a table unless the table layout has fixed-width columns. As I understand it, this is "by design", due to the way the table reflow algorithm is implemented.

Maybe we could we set fixed width to columns? Would that break something?

Deferring again. I don't see a cross browser solution here. Setting the table-layout:fixed is ugly (all the columns are the same width).

In PIWIK 1.0, we can display entire "Pages titles" by adding
" 'actionToLoad' => 'getPageTitles&'"
in plugins/Actions/Actions.php (l 138)

The entire line :
Piwik_AddMenu('Actions_Actions', 'Actions_SubmenuPageTitles', array('module' => 'Actions', 'action' => 'getPageTitles', 'actionToLoad' => 'getPageTitles&

ch33k0n, what are you talking about?