🐛 BUG: markdown rendering gone awry
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, markdown, web-dev
- Domain
- frontend
Research direction
Start by opening the linked daily.dev post and comparing its Markdown rendering with the attached screenshot. The report says it looked correct in the preview but rendered incorrectly after posting, though it does not identify the affected file or component. Trace the post rendering path and check whether the issue can be reproduced; done means the post renders correctly.
Written by the indexing model from the issue text.
Description
What went wrong? 🤔
What happened here, guys?
This looked fine when I previewed it, when I posted it last night.
Expected Behavior
Markdown rendering correctly 😁
Steps to Reproduce Issue
1. Open the link
Solution Proposed
No response
Screenshots
No response
Environment
No response
Browsers
Other
OS
Android
Version of daily.dev
browser
Additional Context
I'm using Vivaldi on Android
I wrote the post from a Windows desktop with Chrome last night though
Code of Conduct
- I follow the conditions of this project.
- Dominant language
- JavaScript
- Stars
- 20.1k
- Forks
- 571
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 dailydotdev/daily
-
Type: Bug
Difficulty 3/5 1-2 days Newbie friendliness 56/100
dailydotdev/daily#2164 ·
Maintainers usually reply within 1 day
-
Status: Accepted Type: Feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
dailydotdev/daily#2077 · 4 comments ·
Maintainers usually reply within 1 day
-
Status: Accepted Type: Bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
dailydotdev/daily#1958 · 2 comments ·
Maintainers usually reply within 1 day
-
🐛 BUG: unable to re-submit registration form if username already takenMay be free again @abhishek-kumar-91 claimed this 612 days ago, and no pull request is open. OpenStatus: Accepted Type: Bug
dailydotdev/daily#1755 · 5 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Status: Accepted
Difficulty 4/5 3-5 days Newbie friendliness 35/100
dailydotdev/daily#1413 · 6 comments ·
Maintainers usually reply within 1 day
All issues in dailydotdev/daily
Similar issues
-
bug Frontend P2-medium UI UX
Difficulty 1/5 Under an hour Newbie friendliness 76/100
Deepak3699/Ai_Mentor#427 ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
11ty/buildawesome#4407 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
keyxmakerx/Chronicle#1711 ·
Maintainers usually reply within 1 day
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
uoftblueprint/canada-basketball#79 ·
Maintainers usually reply within 1 day
-
New App Request
Difficulty 1/5 Under an hour Newbie friendliness 76/100
ThatGuySam/doesitarm#1126 · 1 comment ·