Quarto Website: Prevent margin-sidebar from blocking code copy to clipboard

[nickjhathaway]

When creating a Quarto website project with the code copy to the clipboard turned on I noticed that I couldn't actually get to the copy button and it appears to be an issue with the margin-side bar on the right side. When hovering over the code block the clipboard button appears.

but as you approach it, it then disappears.

This seems to happen where the margin-sidebar on the right is.

When I use the dev tools to delete the sidebar, then I'm able to get over to the copy to clipboard button and I tested this in chrome, firefox, and safari.

I'm wondering if I'm doing anything wrong with the setup and if there is anything I can do to fix this. I'm not currently using anything in the right margin sidebar and wonder if there's a straightforward way to just delete it on every page by default, I'm not very familiar with quarto yet.

My YAML for the site looks like this

project:
  type: website
  output-dir: SeekDeep
  bibliography: references.bib
  resources: ["images"]
  render: 
    - index.qmd
    ...... 
    ...... 
    ...... 
    ...... 

website:
  title: "SeekDeep"
  navbar:
    left:
      - text: "{{< fa home >}} Home"
        href: index.html
    ...... 
    ...... 
    ...... 
    ...... 

format:
  html:
    toc: true
    toc-depth: 4 
    toc-title: Contents
    toc-location: left 
    anchor-sections: true
    smooth-scroll: true
    self-contained: true
    theme: flatly
    highlight-style: textmate
    code-fold: show
    fig-width: 12
    fig-height: 8
    page-layout: full
    bibliography: references.bib

[cderv]

@dragonstyle do you know if the margin side bar could indeed conflict with the copy button ?

[dragonstyle]

It definitely could as its z-order is higher. It looks like the combination of page-layout: full and toc: left is what is required to cause this. I'm opening an issue and we'll try to get it fixed shortly!

[cderv]

Great thanks. Issue #2388 will be the place to track this now. I am locking this thread.

Thanks @nickjhathaway for the feedback !