# \#release-1.0

**URL:** https://talk.commonmark.org/tag/release-1-0/1.md

[Latest](https://talk.commonmark.org/latest.md) · [Categories](https://talk.commonmark.org/categories.md) · [Tags](https://talk.commonmark.org/tags.md)

---

## [Shall CommonMark inline inside HTML5 render as CommonMark? If not, why not?](https://talk.commonmark.org/t/shall-commonmark-inline-inside-html5-render-as-commonmark-if-not-why-not/8964)

<div class="topic-metadata">

**Author:** [@rokejulianlockhart](https://talk.commonmark.org/u/rokejulianlockhart)\
**Replies:** 1\
**Last updated:** [June 26, 2026, 12:54pm UTC](https://talk.commonmark.org/t/shall-commonmark-inline-inside-html5-render-as-commonmark-if-not-why-not/8964 "2026-06-26T12:54:12Z")

</div>

At github.com/MALSync/MALSync/issues/2092: …via the available “GitHub-Flavoured Markdown” markup syntax, I am able to utilise CommonMark inside a \<code\> tag, directly inline: 1. \<code\>\[por\](https://www.loc.gov/standa…

---

## [Issues we MUST resolve before 1.0 release \[6 remaining\]](https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287)

<div class="topic-metadata">

**Author:** [@jgm](https://talk.commonmark.org/u/jgm)\
**Replies:** 25\
**Last updated:** [October 13, 2025, 12:09pm UTC](https://talk.commonmark.org/t/issues-we-must-resolve-before-1-0-release-6-remaining/1287 "2025-10-13T12:09:50Z")

</div>

Here are some issues in the spec that must be resolved before a 1.0 release. To keep us focused, the optional should resolve issues are in this topic and successfully resolved issues are in this topic. To keep things …

---

## [Can a YAML preamble be defined not at the start?](https://talk.commonmark.org/t/can-a-yaml-preamble-be-defined-not-at-the-start/4629)

<div class="topic-metadata">

**Author:** [@rokejulianlockhart](https://talk.commonmark.org/u/rokejulianlockhart)\
**Replies:** 5\
**Last updated:** [September 12, 2025, 11:50am UTC](https://talk.commonmark.org/t/can-a-yaml-preamble-be-defined-not-at-the-start/4629 "2025-09-12T11:50:24Z")

</div>

Sometimes, there are things I’d like to put first.

---

## [How many people here think that CommonMark is plain-text readable?](https://talk.commonmark.org/t/how-many-people-here-think-that-commonmark-is-plain-text-readable/4955)

<div class="topic-metadata">

**Author:** [@rokejulianlockhart](https://talk.commonmark.org/u/rokejulianlockhart)\
**Replies:** 6\
**Last updated:** [March 13, 2025, 4:36pm UTC](https://talk.commonmark.org/t/how-many-people-here-think-that-commonmark-is-plain-text-readable/4955 "2025-03-13T16:36:40Z")

</div>

poll Context I’ve used Markdown dialects for a few years across Discourse, GitHub, GitLab, Plume, WriteFreely, and Bugzilla, et cetera. However, solely as a markup language designed to be rendered. Although I’ve never h…

---

## [The case for calling it Version 1.0](https://talk.commonmark.org/t/the-case-for-calling-it-version-1-0/4957)

<div class="topic-metadata">

**Author:** [@vas](https://talk.commonmark.org/u/vas)\
**Replies:** 0\
**Last updated:** [March 13, 2025, 12:57am UTC](https://talk.commonmark.org/t/the-case-for-calling-it-version-1-0/4957 "2025-03-13T00:57:31Z")

</div>

Please don’t pile “i agree” or “no!” comments onto the GitHub issue unless you have a new argument for or against, or some other useful additional info. JGM doesn’t need the noise. Use the emoticon reactions to registe…

---

## [When do you think we'll ship 1.0 of the CommonMark spec?](https://talk.commonmark.org/t/when-do-you-think-well-ship-1-0-of-the-commonmark-spec/2797)

<div class="topic-metadata">

**Author:** [@mcwumbly](https://talk.commonmark.org/u/mcwumbly)\
**Replies:** 18\
**Last updated:** [February 3, 2025, 2:33am UTC](https://talk.commonmark.org/t/when-do-you-think-well-ship-1-0-of-the-commonmark-spec/2797 "2025-02-03T02:33:21Z")

</div>

From my observation, the community here has rightly been focused on the concrete remaining blockers for a v1.0 of the CommonMark spec, via Issues we MUST resolve before 1.0 release \[8 remaining\] and related topics. Rath…

---

## [Is depth-agnostic heading syntax possible?](https://talk.commonmark.org/t/is-depth-agnostic-heading-syntax-possible/4797)

<div class="topic-metadata">

**Author:** [@rokejulianlockhart](https://talk.commonmark.org/u/rokejulianlockhart)\
**Replies:** 10\
**Last updated:** [December 13, 2024, 11:01pm UTC](https://talk.commonmark.org/t/is-depth-agnostic-heading-syntax-possible/4797 "2024-12-13T23:01:25Z")

</div>

As the undermentioned demonstrates, significant interest in a hierarchy-independent heading tag exists for the WHATWG’s Living Standard HTML5 specification: However, Markdown’s heading syntaxes (the 1 to 6 × #, and -/=…

---

## [Tree Table Support](https://talk.commonmark.org/t/tree-table-support/4630)

<div class="topic-metadata">

**Author:** [@rokejulianlockhart](https://talk.commonmark.org/u/rokejulianlockhart)\
**Replies:** 0\
**Last updated:** [March 24, 2024, 4:36pm UTC](https://talk.commonmark.org/t/tree-table-support/4630 "2024-03-24T16:36:27Z")

</div>

I’d like to be able to render a tree table like: \*\*Name\*\* | \*\*Size\*\* | \*\*Modified\*\* --------------- | -------- | ---------------------------- file\_name\_1 | 1 Pibit | +2024-01-01T00:00:00.0+00:00 file\_nam…

---

## [Are hierarchical bibliographies possible?](https://talk.commonmark.org/t/are-hierarchical-bibliographies-possible/4628)

<div class="topic-metadata">

**Author:** [@rokejulianlockhart](https://talk.commonmark.org/u/rokejulianlockhart)\
**Replies:** 4\
**Last updated:** [March 21, 2024, 12:31am UTC](https://talk.commonmark.org/t/are-hierarchical-bibliographies-possible/4628 "2024-03-21T00:31:33Z")

</div>

I’ve tried \[^Parent.Child\] but that’s only useful for the editor, since it doesn’t change anything for the reader.

---

## [An interesting idea - markdown specification with RGB based support](https://talk.commonmark.org/t/an-interesting-idea-markdown-specification-with-rgb-based-support/4124)

<div class="topic-metadata">

**Author:** [@anon20778841](https://talk.commonmark.org/u/anon20778841)\
**Replies:** 7\
**Last updated:** [April 28, 2022, 6:41am UTC](https://talk.commonmark.org/t/an-interesting-idea-markdown-specification-with-rgb-based-support/4124 "2022-04-28T06:41:22Z")

</div>

Hi Community Commonmark. Feature name Markdown specification with todo support RGB(red, green, blue) Feature description I recently had this idea - adding todo RGB support in Markdown, I don’t know if it’s a good idea …

---

## [Adding editor support for tables](https://talk.commonmark.org/t/adding-editor-support-for-tables/3947)

<div class="topic-metadata">

**Author:** [@anon60592718](https://talk.commonmark.org/u/anon60592718)\
**Replies:** 7\
**Last updated:** [August 25, 2021, 8:30pm UTC](https://talk.commonmark.org/t/adding-editor-support-for-tables/3947 "2021-08-25T20:30:02Z")

</div>

I love markdown, but something that makes me uncomfortable using markdown is bummer about having to write any table, I would have to start row by row and column by column. Another problem I notice is that if you have a l…

---

## [Quotes in the title attribute](https://talk.commonmark.org/t/quotes-in-the-title-attribute/3788)

<div class="topic-metadata">

**Author:** [@e.k](https://talk.commonmark.org/u/e.k)\
**Replies:** 0\
**Last updated:** [February 15, 2021, 2:14pm UTC](https://talk.commonmark.org/t/quotes-in-the-title-attribute/3788 "2021-02-15T14:14:17Z")

</div>

This is to discuss quotes in the title attribute. In Markdown.pl, title is used for links and images. From “Issues we MUST resolve before 1.0 release”: I think both backslash escapes and nested quotes should be allowe…

---

## [Blank lines before lists, revisited](https://talk.commonmark.org/t/blank-lines-before-lists-revisited/1990)

<div class="topic-metadata">

**Author:** [@jgm](https://talk.commonmark.org/u/jgm)\
**Replies:** 35\
**Last updated:** [January 17, 2021, 11:03pm UTC](https://talk.commonmark.org/t/blank-lines-before-lists-revisited/1990 "2021-01-17T23:03:00Z")

</div>

Currently CommonMark does not require a blank line between a regular paragraph and a list. In this respect it differs from most current implementations. John Gruber made his intentions clear on this, too; although the…

---

## [A problem with backtick code fences](https://talk.commonmark.org/t/a-problem-with-backtick-code-fences/1053)

<div class="topic-metadata">

**Author:** [@jgm](https://talk.commonmark.org/u/jgm)\
**Replies:** 46\
**Last updated:** [April 30, 2019, 6:22am UTC](https://talk.commonmark.org/t/a-problem-with-backtick-code-fences/1053 "2019-04-30T06:22:13Z")

</div>

First, a bit of history. Way back before github even existed, Michel Fortin (of PHP Markdown Extra) and I discussed the idea of a "fenced" or "delimited" code block syntax. We eventually decided on tildes as delimiters,…

---

## [2019 commonmark - state of the union](https://talk.commonmark.org/t/2019-commonmark-state-of-the-union/3110)

<div class="topic-metadata">

**Author:** [@felix42](https://talk.commonmark.org/u/felix42)\
**Replies:** 1\
**Last updated:** [March 19, 2019, 5:40am UTC](https://talk.commonmark.org/t/2019-commonmark-state-of-the-union/3110 "2019-03-19T05:40:31Z")

</div>

This topic is thought as a request by a new (commonmark)-user to find out about the state of the implementation. As I understand the webpage the spec for commonmark is pretty stable (even though the commonmark python pr…

---

## [Tab-related issues](https://talk.commonmark.org/t/tab-related-issues/1831)

<div class="topic-metadata">

**Author:** [@jgm](https://talk.commonmark.org/u/jgm)\
**Replies:** 7\
**Last updated:** [January 9, 2019, 7:51am UTC](https://talk.commonmark.org/t/tab-related-issues/1831 "2019-01-09T07:51:15Z")

</div>

Here’s a nice case: \>\[TAB\]\[TAB\]x http://johnmacfarlane.net/babelmark2/?normalize=1&text=\> x Here is a summary of the different approaches different implementations take: Treat this exactly as if it’s expanded to …

---

## [Leading and trailing white spaces in code blocks](https://talk.commonmark.org/t/leading-and-trailing-white-spaces-in-code-blocks/628)

<div class="topic-metadata">

**Author:** [@nightw](https://talk.commonmark.org/u/nightw)\
**Replies:** 23\
**Last updated:** [November 5, 2018, 5:47am UTC](https://talk.commonmark.org/t/leading-and-trailing-white-spaces-in-code-blocks/628 "2018-11-05T05:47:06Z")

</div>

I would like to ask about the title int the specs. Is it intended that the leading and trailing white spaces are trimmed even in code blocks? I would argue that the code blocks should be something like the \<pre\> tags and…

---

## [Info strings for suffixed headings](https://talk.commonmark.org/t/info-strings-for-suffixed-headings/2902)

<div class="topic-metadata">

**Author:** [@Crissov](https://talk.commonmark.org/u/Crissov)\
**Replies:** 6\
**Last updated:** [September 4, 2018, 4:51pm UTC](https://talk.commonmark.org/t/info-strings-for-suffixed-headings/2902 "2018-09-04T16:51:33Z")

</div>

https://github.com/commonmark/CommonMark/issues/500 Related topics Info strings elsewhere Consistent attribute syntax Feature request: automatically generated ids for headers Anchors in markdown Enumerated lists withou…

---

## [CDATA and processing instructions should not be recognized](https://talk.commonmark.org/t/cdata-and-processing-instructions-should-not-be-recognized/2546)

<div class="topic-metadata">

**Author:** [@Demi\_Obenour](https://talk.commonmark.org/u/Demi_Obenour)\
**Replies:** 1\
**Last updated:** [August 15, 2017, 1:03am UTC](https://talk.commonmark.org/t/cdata-and-processing-instructions-should-not-be-recognized/2546 "2017-08-15T01:03:52Z")

</div>

According to the HTML specification, CDATA sections and processing instructions are parse errors, which means that they should never occur in a valid HTML document. CommonMark should not recognize them, or (in the case …

---

## [What are "blanks"?](https://talk.commonmark.org/t/what-are-blanks/2478)

<div class="topic-metadata">

**Author:** [@Arandur](https://talk.commonmark.org/u/Arandur)\
**Replies:** 3\
**Last updated:** [June 19, 2017, 1:25pm UTC](https://talk.commonmark.org/t/what-are-blanks/2478 "2017-06-19T13:25:38Z")

</div>

Section 4.2 ATX Headings states: Leading and trailing blanks are ignored in parsing inline content and then gives # foo =\> \<h1\>foo\</h1\> as an example. The term “blank” appears i…

---

## [Should there be additional information in the AST?](https://talk.commonmark.org/t/should-there-be-additional-information-in-the-ast/2138)

<div class="topic-metadata">

**Author:** [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Replies:** 21\
**Last updated:** [March 13, 2017, 1:06am UTC](https://talk.commonmark.org/t/should-there-be-additional-information-in-the-ast/2138 "2017-03-13T01:06:08Z")

</div>

Continuing the discussion from Issues we SHOULD resolve before 1.0 release: Currently we lose information about: whether a link was an autolink whether it was a reference link, what kind, and what label what the bul…

---

## [Special treatment of void elements in HTML blocks](https://talk.commonmark.org/t/special-treatment-of-void-elements-in-html-blocks/2288)

<div class="topic-metadata">

**Author:** [@jgm](https://talk.commonmark.org/u/jgm)\
**Replies:** 1\
**Last updated:** [November 8, 2016, 11:49am UTC](https://talk.commonmark.org/t/special-treatment-of-void-elements-in-html-blocks/2288 "2016-11-08T11:49:52Z")

</div>

Comments welcome on this proposal for a revision to the spec for raw HTML blocks:

---

## [Issues RESOLVED for 1.0 release](https://talk.commonmark.org/t/issues-resolved-for-1-0-release/2137)

<div class="topic-metadata">

**Author:** [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Replies:** 0\
**Last updated:** [June 28, 2016, 9:58am UTC](https://talk.commonmark.org/t/issues-resolved-for-1-0-release/2137 "2016-06-28T09:58:28Z")

</div>

This is a companion topic for the CommonMark 1.0 release. These are issues that were successfully resolved as we worked toward the 1.0 release. To keep things organized, please comment in the linked discussions or iss…

---

## [Issues we SHOULD resolve before 1.0 release](https://talk.commonmark.org/t/issues-we-should-resolve-before-1-0-release/2136)

<div class="topic-metadata">

**Author:** [@codinghorror](https://talk.commonmark.org/u/codinghorror)\
**Replies:** 0\
**Last updated:** [June 28, 2016, 9:52am UTC](https://talk.commonmark.org/t/issues-we-should-resolve-before-1-0-release/2136 "2016-06-28T09:52:48Z")

</div>

This is a companion topic for the CommonMark 1.0 release. These are issues that SHOULD be resolved before the 1.0 release, if possible, but are not required to release CommonMark 1.0. Turn empty link definitions into…

---

## [Ordered list detection has precedence over title detection](https://talk.commonmark.org/t/ordered-list-detection-has-precedence-over-title-detection/1251)

<div class="topic-metadata">

**Author:** [@tremby](https://talk.commonmark.org/u/tremby)\
**Replies:** 25\
**Last updated:** [February 3, 2016, 6:56pm UTC](https://talk.commonmark.org/t/ordered-list-detection-has-precedence-over-title-detection/1251 "2016-02-03T18:56:40Z")

</div>

I'm not sure if this belongs in spec or implementation, since I don't have time to dig through the spec at this moment. I had a client just asking me why the German version of one of her pages is displaying so differen…

---

## [Reconsidering "two blank lines breaks out of lists"](https://talk.commonmark.org/t/reconsidering-two-blank-lines-breaks-out-of-lists/934)

<div class="topic-metadata">

**Author:** [@jgm](https://talk.commonmark.org/u/jgm)\
**Replies:** 10\
**Last updated:** [January 7, 2015, 5:04am UTC](https://talk.commonmark.org/t/reconsidering-two-blank-lines-breaks-out-of-lists/934 "2015-01-07T05:04:36Z")

</div>

The current spec says that two blank lines (except in a fenced code block) terminates all containing lists. I'd like to reconsider this rule. It is inconsistent with the principle of uniformity that guides some of the …
