Why web browsers don't support Markdown
The article explains that web browsers don't natively render Markdown because the web's foundation is HTML, and implementing Markdown support would introduce security risks, performance issues, and inconsistencies across different Markdown flavors. Instead, Markdown is typically converted to HTML before being displayed in browsers.
Background
Markdown is a lightweight markup language created in 2004 by John Gruber and Aaron Swartz, designed to let writers format plain text (headings, bold, links, lists) with simple symbols like `#` or `*`, then convert it to HTML. Despite its popularity among developers and writers, no major web browser (Chrome, Firefox, Safari, Edge) renders Markdown natively in its address bar or page viewer — browsers only understand HTML, CSS, and JavaScript. The article examines why that's the case, explaining that Markdown was never intended as a web-native format, has no single official standard (multiple "flavors" exist, like GitHub-Flavored Markdown), and would require browsers to handle ambiguous parsing, security issues (Markdown can contain raw HTML and thus XSS vectors), and a huge compatibility break with the existing web ecosystem built on HTML.