quarto-dev / quarto-dev/quarto-cli

Scrolling Prohibited in OJS `Inputs.Table()` When Quarto Dashboard Row Height Is Set

Open
#10,317 7 comments 3 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Jul 17, 2024.

bug dashboards ojs-engine
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

Whenever row height is explicitly set in a quarto dashboard using Observable's Inputs.table(), it prevents scrolling through the entire contents of a table rendered through Inputs.table(). If row height is not explicitly set, scrolling occurs as expected.

Steps to reproduce

I've put a repo together showing the differences, which lives here: https://github.com/mrworthington/duckdb-in-ojs

  • The file named index.qmd does not have row height set in the quarto dashboard.
  • The file named "index_2.qmd" does explicitly set a row height.
Expected behavior

When you render a table with Inputs.table(), it should scroll as contents are called upon. Via the Observable docs:

A Table displays tabular data. It’s fast: rows are rendered lazily on scroll. It sorts: click a header to sort, and click again to reverse. And it selects: click a checkbox on any row, and the selected rows are exported as a view value. (And for searching, see the Search input.) For more applied examples, see Hello, Inputs!

By default, all columns are visible. Only the first dozen rows are initially visible, but you can scroll to see more. Column headers are fixed for readability.

When row height isn't set in a quarto dashboard, it behaves as expected (albeit with a weird cutoff that occurs if the table's expanded).

https://github.com/user-attachments/assets/50f86995-fdb4-4509-8327-0b3560c09e37

Actual behavior

However, when row height is explicitly set in the quarto dashboard, the scrolling is prohibited:

https://github.com/user-attachments/assets/3dcf9b5d-afdd-425d-924d-4aeb6e16a733

Your environment
  • IDE: RStudio Version 2024.04.0+735 (2024.04.0+735)
  • Quarto: v 1.6.1 (FWIW, it also occurred on v 1.5)
  • R: 4.4.1
Quarto check output
Quarto 1.6.1
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.2.0: OK
      Dart Sass version 1.70.0: OK
      Deno version 1.41.0: OK
      Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.6.1
      Path: /Applications/quarto/bin

[✓] Checking tools....................OK
      TinyTeX: (not installed)
      Chromium: (not installed)

[✓] Checking LaTeX....................OK
      Tex:  (not detected)

[✓] Checking basic markdown render....OK

[✓] Checking Python 3 installation....OK
      Version: 3.12.3
      Path: /usr/local/bin/python3
      Jupyter: (None)

      Jupyter is not available in this Python installation.
      Install with python3 -m pip install jupyter

[✓] Checking R installation...........OK
      Version: 4.4.1
      Path: /Library/Frameworks/R.framework/Resources
      LibPaths:
        - /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources/library
      knitr: 1.46
      rmarkdown: 2.27

[✓] Checking Knitr engine render......OK

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.