Dashboard with first page as `scrolling="true"` does not scroll until navigating away

[damonbayer]

Bug description

I have created a dashboard where the first page has the scrolling="true" property. The first time I visit the dashboard, the first page does not have the scrolling layout. If I navigate to some other page and return to the first page, the scrolling layout is enabled. This behavior is consistent across multiple web browsers on multiple operating systems.

Steps to reproduce

This document exhibits the behavior. When visiting the rendered html for the first time, the first page does not scroll.

--- 
title: "Dashboard"
format: dashboard
--- 

```{r}
library(ggplot2)
my_plot <- ggplot(mpg, aes(displ, hwy)) + 
  geom_point(aes(color = class))
```

# Scrolling Page {scrolling="true"}

```{r}
my_plot
```

```{r}
my_plot
```


```{r}
my_plot
```

# Non-scrolling Page

```{r}
my_plot
```

```{r}
my_plot
```


```{r}
my_plot
```

Expected behavior

The first page should have the scrolling layout when it is loaded for the first time.

Actual behavior

The first page does not have the scrolling layout when it is loaded for the first time. Navigating to another page and then revisiting the first page causes the scrolling layout to work.

Your environment

Issue persists on Windows with VSCode IDE and Edge browser, as well as macOS with RStudio and Safari browser.

Quarto check output

Quarto 1.6.39
[✓] Checking environment information...
      Quarto cache location: /Users/damon/Library/Caches/quarto
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.4.0: OK
      Dart Sass version 1.70.0: OK
      Deno version 1.46.3: OK
      Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.6.39
      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.13.0
      Path: /opt/homebrew/opt/python@3.13/bin/python3.13
      Jupyter: (None)

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

[✓] Checking R installation...........OK
      Version: 4.4.2
      Path: /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources
      LibPaths:
        - /Users/damon/Library/R/arm64/4.4/library
        - /Library/Frameworks/R.framework/Versions/4.4-arm64/Resources/library
      knitr: 1.49
      rmarkdown: 2.29

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

[mcanouil]

Could you properly format your post using code blocks for code and terminal outputs? Thanks.
If your code contains code blocks, you need to enclose it using more backticks, i.e., usually four ````.
See https://quarto.org/bug-reports.html#formatting-make-githubs-markdown-work-for-us.

[damonbayer]

@mcanouil Done. Sorry about that!