[
https://issues.apache.org/jira/browse/TRINIDAD-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801723#action_12801723
]
Cedric Durmont commented on TRINIDAD-1107:
------------------------------------------
hmmm... yes, my solution is far from perfect for now. One of my colleague
performed some more tests, and found out that :
- Chrome (dev version) puts the column headers on top of page
- IE8 in standards compliant mode does the same
- headers are duplicated after a column sort (ouch !)
Well, looks like I have more to do on that issue that I've thought ! Will try
to find simple fixes for those problems, but this demands deeper modifications,
I think I'd go for a rewrite.
The current solution is quite ugly (no offense, the code was obviously made for
and works well with IE6, which is quite remarkable) : 2 tables, 2 divs, 1
iframe, and some Javascript to fill and position the iframe at the right place.
I saw examples of scrollable tables using only thead/tbody/tfoot and a bunch of
CSS which could provide a cleaner and possibly better solution (I'm not sure of
what happens with the current code if we use all of the tr:table possibilities,
e.g. nested columns and the likes...
> tr:table - scrolling of content
> -------------------------------
>
> Key: TRINIDAD-1107
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1107
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Components
> Reporter: Gerhard Petracek
> Attachments: patch.txt
>
>
> if a table is too long and it comes to page scrollbars, you cannot see the
> header all the time (e.g. after scrolling to the bottom of the table).
> so we need a scrollbar for the table body.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
