Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In-table scrolling

Wiki MarkupMany of the tables used in DM-BI applications include loads of data. Rather than scrolling entire pages, we have included in-table scrolling in RAFT. This allows us to present multiple tables on the same page. Code \[insert\] Example \[insert\] Related patterns \[insert\] Problem Much of the data presented in DM-BI applications is tabular. Some pages require more than one table on a page  Solution In-table scrolling allows us to set a limit for the number of rows presented at once. This improves the readability of the viewable data for users by limiting the amount of information they see at one time. This also allows them to keep column headers in view (which allow sorting). Rationale We considered showing the full-length tables, requiring users to scroll down the page to see their information. However, they lost sight of the table headers which allow sorting and other metadata and instruction copy. Accessibility \[insert\] Many of the tables used in DM-BI applications include long tables of data. Rather than scrolling entire pages, we have included in-table scrolling in RAFT. This allows us to present both long tables and multiple tables on the same page.

Code

Wiki Markup
\[insert\]

Example

Wiki Markup
\[insert\]

Related patterns

Tables

Wiki Markup\[insert\]See Tables

Problem

Much of the data presented in DM-BI applications is tabular. Some pages require more than one table on a page. It can be difficult to navigate long pages while maintaining context. As users scroll down the page, when the entire page scrolls, they can lose the table headers and other contextual information.

Solution

In-table scrolling allows us to set a limit for the number of rows presented at once. This improves the readability of the viewable data for users by limiting the amount of information they see at one time. This also allows them to keep column headers in view (which allow sorting). This also keeps instruction copy and other page-level information in sight.

Rationale

We considered showing the full-length tables, requiring users to scroll down the page to see their information. However, they lost sight of the table headers which allow sorting and other metadata and instruction copy.

Accessibility

Wiki Markup
\[insert\]