copyable shortcode doesn't work when the strings are inside a cell of a markdown table.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 57/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by locating how project descriptions and instructions render Markdown tables and how the copyable shortcode is handled. Reproduce the issue with the shortcode in a table cell, then compare it with the working standalone paragraph behavior. Done means the shortcode works when placed in a table cell; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Description
What happened?
While trying to improve the readability of a project's instruction for mappers, I've noted that some users may overlook additional details that needs scrolling down (probably due to their layout or screen size).
The image below is the preview of the revision. The top part shows a markdown table, and the cells showing the literal copyable shortcode. The bottom section of the image shows the original section, where the copyable are separate paragraphs, and works as intended.
I expected copyable shortcodes to work inside markdown tables, too.
Steps to reproduce
- Add a markdown table in the description or instructions section of your project
- Add the copyable shortcode as cell in any row
Environment
Firefox, Vivalid. Android and Desktop (Pop OS!)
Additional information
No response
- Dominant language
- JavaScript
- Stars
- 168
- Forks
- 41
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 23
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from maproulette/maproulette-frontend
-
"How should your Challenge be Categorized?" resets to OtherPossibly taken @krishan05530 claimed this 9 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
maproulette/maproulette-frontend#2944 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
maproulette/maproulette-frontend#2943 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
maproulette/maproulette-frontend#2923 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 58/100
maproulette/maproulette-frontend#2949 ·
Maintainers usually reply within 1 day
-
bug v4
Difficulty 3/5 1-2 days Newbie friendliness 42/100
maproulette/maproulette-frontend#2941 · 1 comment ·
Maintainers usually reply within 1 day
All issues in maproulette/maproulette-frontend
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
glossyio/traffic-monitor#264 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
micromatch/picomatch#243 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
getComputedStyle().display is "" for span, a, b, label and other inline elements instead of "inline"Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
capricorn86/happy-dom#2556 ·
Maintainers usually reply within 1 day