WordPress/gutenberg

Backticks in Code block produce nested <code> tags

Open

#28,926 opened on Feb 10, 2021

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (3,893 forks)batch import
Good First Issue[Block] Code[Status] In Progress[Type] Regression

Repository metrics

Stars
 (9,607 stars)
PR merge metrics
 (Avg merge 12d 18h) (509 merged PRs in 30d)

Description

Description

If you try to add open and closing backticks inside of a "Code" block, then it produces a nested <code> block inside of it. The same is true of the Preformatted block

Step-by-step reproduction instructions

  1. Create a new code block (or preformatted block)
  2. Add text inside of two backticks
  3. The text will be transformed into a <code> element, nested inside of the block

Expected behaviour

Backticks should retain their original formatting and not transform.

Actual behaviour

Backticks are converted into a <code> element

Screenshots or screen recording (optional)

Code snippet (optional)

WordPress information

  • WordPress version: 5.6
  • Gutenberg version: Not Installed
  • Are all plugins except Gutenberg deactivated? Yes
  • Are you using a default theme (e.g. Twenty Twenty-One)? Yes

Device information

  • Device: Desktop
  • Operating system: MacOS 11.2
  • Browser: Firefox 86

Contributor guide

Research direction
Investigate the code that converts backticks to inline <code> tags in the editor and ensure that inside code blocks (and preformatted blocks) this conversion is skipped so that backticks remain literal.
Tech stack
javascript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70