processing / processing/p5.js-website

`<canvas>` tag rendered instead of escaped in `p5.Graphics` reference page

Open Beginner friendly
#1,389 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug
Dominant language
MDX
Stars
96
Forks
322
Avg merge
5d 22h
Merged PRs (30d)
8

Description

Most appropriate sections of the p5.js website?

Reference

What is your operating system?

Mac OS

Web browser and version

147.0.7727.138 (Official Build) (arm64)

Actual Behavior

The <canvas> tag in the p5.Graphics.remove() reference text is being rendered as a real canvas element on the page.

Image
Expected Behavior

The reference page should show the code example as text only. The <canvas> element should be escaped, not inserted into the page as an actual canvas.

Steps to reproduce

Visit https://p5js.org/reference/p5/p5.Graphics/ and scroll down to Methods>remove.

Notes

Whoever works on this issue should audit the website for other reference pages suffering from the same issue.

Would you like to work on the issue?

No, I'm just reporting the issue

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 at the p5.Graphics reference page and inspect the p5.Graphics.remove() entry, where the tag is rendered in the reference text. Check nearby reference pages for the same behavior, then verify that the example appears as escaped text and no real canvas element is inserted.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
74/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.