quarto-dev / quarto-dev/quarto

Visual editor un-nests spans

Open
#762 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug visual-editor
Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

Bug description

When authoring slides in revealjs format, the following slide, featuring nested spans, renders as intended: each fragment fading in on click, each with a colored span, all in the same paragraph.

---
format: revealjs
---

## Title

::: {style="text-align: center"}
[One [hen]{style="color: red"}]{.fragment} [two [ducks]{style="color: blue"}]{.fragment}
:::

When I click into the visual editor, then click back, the sourced has been changed to:

---
format: revealjs
---

## Title

::: {style="text-align: center"}
[One ]{.fragment}[hen]{style="color: red"} [two ]{.fragment}[ducks]{style="color: blue"}
:::

In other words, it unnests the spans, which has the effect of breaking the animation.

I can fix the animation by putting the fade in fragments as divs instead of spans, but then it breaks the all-in-one-paragraph layout.

This is using the RStudio IDE 2022.07.0 Build 548 "Spotted Wakerobin" on MacOS Catalina 10.15.7.

Thanks for the help!

quarto check Output
[✓] Checking Quarto installation......OK
      Version: 1.0.20
      Path: /Applications/quarto/bin

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

[✓] Checking Python 3 installation....OK
      Version: 3.9.1
      Path: /usr/local/bin/python3
      Jupyter: 4.11.0
      Kernels: python3

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

[✓] Checking R installation...........OK
      Version: 4.2.1
      Path: /Library/Frameworks/R.framework/Resources
      LibPaths:
        - /Library/Frameworks/R.framework/Versions/4.2/Resources/library
      rmarkdown: 2.14

[✓] Checking Knitr engine render......OK
quarto tools check Output
[✓] Inspecting tools

Tool         Status            Installed     Latest  
chromium     Not installed     ---           869685  
tinytex      Not installed     ---           v2022.07

Contributor guide

No contributing guide indexed for this repository

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 by reproducing the issue with the nested-span Markdown example in the visual editor, then trace the editor's source-to-visual-to-source conversion path. No source file or test is named in the report; done means nested fragment and colored spans remain nested and the revealjs animation and single-paragraph layout are preserved.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
frontend
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.