[alonso100]

Hello,

I create HTML tables per code which later I assign to the HTML widget. As long as the table has few records, these can be displayed correctly in portrait. In landscape or in case of many records part of it is not displayed, so I have to use a panel for being able to scroll. When using the panel, this destroys entirely the look&feel as well as functionality of the table:

1) height of cells is at least 2 times higher than without the panel
2) in portrait, if the table is too wide scrolling left/right is almost impossible. The scroll bar does not react inmediately.
3) In landscape, if I scroll downwards I cannot scroll upwards anymore since the information is “lost”. It seems like the coordinates of the content and the HTML widget go lost. The more I try to scroll up the smaller the visible area of the table.
4) if I ever scroll right, I cannot normally scroll left anymore.

I don´t have those problems when creating the table without a panel. So, what is the reason for this and how to solve it ??

I include the code in this posting.

Attachments:

You must be logged in to view attached files.

[support-michael]

@alonso100

We debugged what’s up and here are few tips:

>1) height of cells is at least 2 times higher than without the panel

The issue is cause by an inherited inherited css value from parent elements. To avoid this, manually set a top level <div> in your code

      <div align="center" style="line-height: normal">
      // all other table's code goes here

The scrolling is bigger challenge. The webkit based browser does not support scrolling on a div. Also note that the scrolling panel does not support horizontal scrolling at this time. So what to do?

For long html content embed it in a panel. The panel height needs to be sized to a level that enables the HTML widget to expand to reveal all of its content. The html content should not overflow the panel. Nor should it try to provide its own scroller. As you have identifed that will conflict with the panel scroller.

I hope this clarifies use of the html widget. We will update our docs to provide better guidance for integrating custom html.

[Author]

Posts