Age | Commit message (Collapse) | Author | |
---|---|---|---|
2019-12-16 | Remove outdated restriction on list item (#627) | Johel Ernesto Guerrero Peña | |
This is a holdover from the days when two blank lines broke out of a list. Case missed by 780b981. | |||
2019-12-04 | Change "a HTML block" to "an HTML block" (#623) | Anthony Fok | |
for consistency with the rest of the spec. | |||
2019-11-11 | Add example with unbalanced parens in link destination. | John MacFarlane | |
See commonmark/commonmark.js#177. | |||
2019-11-04 | Fix link (#601) | Titus | |
2019-10-31 | Remove superfluous restrictions on declarations (#621) | Titus | |
HTML declarations need not be limited to all capital ASCII letters. Closes #620. | |||
2019-10-01 | Fix typo in control characters (#617) | Titus | |
2019-09-09 | Add definition of ASCII control characters (#603) | Titus | |
Relted-to GH-602. | |||
2019-09-09 | Move "Backslash escapes" and "Character references" to "Preliminaries." | John MacFarlane | |
It was confusing having them in the "Inline" section, since they also affect some block contexts (e.g. reference link definitions). Closes #600. | |||
2019-08-05 | Clarify that new blocks are added to *container* blocks. (#598) | Jay Weisskopf | |
My first attempt at writing a parser added new blocks to the last matched block, regardless if it was a container or leaf. I think it would have helped me if it had explicitly said "container" here. | |||
2019-06-05 | Clarify language for backtick code spans (#589) | Johel Ernesto Guerrero Peña | |
"These" may be clearer than "the" in cases where code span contains internal strings of backticks. | |||
2019-05-15 | fix link text grouping sample (#584) | Ashe Connor | |
From @johelegp at https://github.com/github/cmark-gfm/pull/157. | |||
2019-04-30 | Fix misleading text for full reference link. | John MacFarlane | |
There is no "first link label" here, just a link text. Closes #581. | |||
2019-04-30 | Use better example to test unicode case fold for ref links. | John MacFarlane | |
The earlier test could be passed by implementations that just uppercase. Fixes #582. | |||
2019-04-11 | Test new entity length constraints (#575) | Miha Zupan | |
This now tests that an entity with 8 arabic digits is no longer recognised | |||
2019-04-07 | Added backslash escape + char entity case. | John MacFarlane | |
2019-04-06 | Bump to 0.29. | John MacFarlane | |
2019-04-06 | Specify dropping of initial/final whitespace in setext heading content. | John MacFarlane | |
Closes #461. | |||
2019-04-06 | Removed redundant condition. | John MacFarlane | |
We don't need to specify that the absolute URI in an autolink doesn't contain `<`, since this is specified in the description of an absolute URI. | |||
2019-04-06 | Added example with a ref link defn where the reference is never used. | John MacFarlane | |
Closes #454. | |||
2019-04-06 | Example with setext header after reference link defs. | John MacFarlane | |
Closes #395. | |||
2019-04-06 | Clarify that entities can't be used to indicate structure. | John MacFarlane | |
For example, you can't use `*` instead of `*` for a bullet list, or ` ` to create a new paragraph. Closes #474. | |||
2019-04-06 | Added additional spec examples involving link destinations in `<>`. | John MacFarlane | |
Closes #473. | |||
2019-04-04 | Adjust another test case for change to spaces in code span. | John MacFarlane | |
2019-04-04 | Don't strip spaces in code span containing only spaces. | John MacFarlane | |
This allows one to include a code span with just spaces, using the most obvious syntax. Fixes #569. | |||
2019-04-04 | Capitalize GitHub | John MacFarlane | |
2019-04-03 | Add example w/ reference link w/ empty destination in `<>`. | John MacFarlane | |
Closes #172. | |||
2019-03-26 | Fix spec example in light of recent change to link destination. | John MacFarlane | |
2019-03-25 | Disallow link destination beginning with `<` unless it is inside `<..>`. | John MacFarlane | |
This brings the description in line with the spec example: ``` [foo]: <bar>(baz) [foo] . <p>[foo]: <bar>(baz)</p> <p>[foo]</p> ``` Closes #538. | |||
2019-03-25 | Clarify that script, pre, style close tags can begin an HTML block. | John MacFarlane | |
Closes #517. | |||
2019-03-23 | codepoints for punctuation characters (#564) | Christoph Päper | |
2019-03-23 | Fix typo in spec (#551) | Grahame Grieve | |
Change "If none in found" to "If none is found" | |||
2019-03-23 | fix typo in spec (#556) | tnaia | |
2019-03-23 | Match interior delimiter runs if lengths of both are multiples of 3. | John MacFarlane | |
This gives better results on `a***b***c` without giving bad results on the cases that motivated the original multiple of 3 rule. Closes #528. | |||
2019-03-20 | Rephrase example #111 to indicate that the rendering is not mandated. | John MacFarlane | |
Closes #568. | |||
2019-03-19 | Fix typo in fix to #562. | John MacFarlane | |
2019-03-19 | Add test for [test](<url\>). Closes #562. | John MacFarlane | |
2019-03-17 | Disallow unescaped `(` in parenthesized link titles. | John MacFarlane | |
Closes #526. | |||
2019-03-17 | Improve documentation of openers_stack. | John MacFarlane | |
Closes #563. | |||
2019-03-17 | Improve documentation of parsing strategy. | John MacFarlane | |
Note that `openers_bottom` needs to be indexed to delimiter run lengths as well as types. Closes #563. | |||
2018-11-25 | Removed vestigial restriction in list item spec. | John MacFarlane | |
The "not separated by more than one blank line" was a left-over from an earlier version of the spec in which two blank lines ended a list. Closes #543. | |||
2018-10-04 | Clarify tlides and backticks in info strings. | John MacFarlane | |
We disallow backticks in info strings after backtick fences only. Both backticks and tildes are allowed in info strings after tilde fences. Added example. Closes #119. | |||
2018-09-09 | Fixed test case for #469. | John MacFarlane | |
2018-09-09 | Example showing need for space before title in reference link. | John MacFarlane | |
Closes #469. | |||
2018-09-09 | Clarify the left- and right-flanking definitions (#534) | Jay Martin | |
* Clarify the left- and right-flanking definitions A few more words make the definitions easier to understand, without changing the meaning. Links to the current definitions: - [left-flanking delimiter run](https://github.github.com/gfm/#left-flanking-delimiter-run) - [right-flanking delimiter run](https://github.github.com/gfm/#right-flanking-delimiter-run) * Change numbering to 1, 2a and 2b 1, 2a and 2b is more conventional than a, b1 and b2, which I suggested earlier. | |||
2018-08-27 | typo fix: occuring -> occurring (#533) | nikolas | |
2018-08-26 | Simplified revisions to code span normalization rules. | John MacFarlane | |
Removed the complex rule about ignoring newlines adjacent to spaces. Now newlines are simply converted to spaces. | |||
2018-08-25 | Code spans: don't collapse interior space. | John MacFarlane | |
Closes #532. | |||
2018-08-13 | update references to container and leaf block headers to use the correct ↵ | Elijah Hamovitz | |
pluralization (#531) | |||
2018-06-11 | Remove `meta` from list of block tags... | John MacFarlane | |
...in start condition #6 of HTML blocks. meta tags are used in some inline contexts (though this isn't valid HTML5), e.g. in schema.org. Example: ``` This paragraph is closed right after an opening span: <span itemprop="contentLocation" itemscope itemtype="https://schema.org/City"> <meta itemprop="name" content="Springfield"> <span itemprop="address" itemscope itemtype="https://schema.org/PostalAddress"> <meta itemprop="addressCountry" content="US"> <span itemprop="addressLocality">Springfield</span>, <span itemprop="addressRegion">Oregon</span> <meta itemprop="postalCode" content="97477"> </span> </span> ``` Closes #527. | |||
2018-03-25 | Fixed typo in recent spec change for spaces in link dest. | John MacFarlane | |