quarto-dev / quarto-dev/quarto-cli

Tabset linking back to first page of presentation?

Open
#1,574 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement revealjs tabsets
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Hi all,
I'm working on a relatively heavily customized template for a qmd revealjs presentation (see here). I think I managed to make things work more or less like I want (there's a slight issue with the logo in the version I'm sharing --- I don't understand why... But it works OK everywhere else I used it so that's not the problem).

The problem I can see with tabset is that if I use the code

include-after: |
    <style>
    .logo {
      background-image: url("assets/images/UCL-stats.png");
      background-size: 14% 7%;
      background-repeat: no-repeat;
      position: absolute;
      top:  1.9%; /* 2.65%em */
      left: 86%;
      height: 100%;
      width: 100%;
      z-index: 20; !default
    }
    </style>

    <script>
    document.querySelectorAll(
      'section.slide.level2:not(section.slide.level2.title-slide.center):not(section.slide.level2.nobar)'
    )
    .forEach(el => {
      el.innerHTML += '<div class="logo"></div>';
    });
    </script>

in my yaml, which is used to add the logo to the top-right of each slide, then, when I view the presentation on my browser (Firefox), clicking on either of the two tabs brings me back to the title page. If I remove the code above, then the tabset works OK and clicking on the tabset's title moves from one to the other.

The other slight issue (not sure whether I'm missing something obvious here, though) is whether you can use the keyboard arrows to navigate through tabsets? (I come from xaringan and there you can do that so I wondered whether that's a feature that is possible under qmd too?).

Many thanks!
Gianluca

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.

Research direction

Start with the linked test.qmd and reproduce the revealjs presentation in Firefox with the include-after CSS and script enabled, then compare it with those additions removed. Trace the tabset navigation behavior and determine whether keyboard-arrow navigation is supported; done means the tabs no longer return to the title page and the keyboard behavior is documented or corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.