Open thibaudcolas opened 2 years ago
Similarly to my response in #533, there is compliance with sphinx/docutils but not quite with CommonMark:
=== ===
foo bar
=== ===
baz bim
=== ===
generates
$ rst2pseudoxml.py test.rst
<document source="test.rst">
<table>
<tgroup cols="2">
<colspec colwidth="3">
<colspec colwidth="3">
<thead>
<row>
<entry>
<paragraph>
foo
<entry>
<paragraph>
bar
<tbody>
<row>
<entry>
<paragraph>
baz
<entry>
<paragraph>
bim
and
| foo | bar |
| --- | --- |
| baz | bim |
generates
$ myst-docutils-pseudoxml test.rst
<document source="test.rst">
<table classes="colwidths-auto">
<tgroup cols="2">
<colspec colwidth="50.0">
<colspec colwidth="50.0">
<thead>
<row>
<entry>
<paragraph>
foo
<entry>
<paragraph>
bar
<tbody>
<row>
<entry>
<paragraph>
baz
<entry>
<paragraph>
bim
trying to remove the paragraph nodes, will likely cause issues with the docutils/sphinx build, that is expecting them.
again here, one could add hidden=True
to the paragraph
nodes, but then it is how to have this respected by docutils/sphinx
Describe the bug
context
This is the same issue as #533, but for tables. I would like to use MyST’s implementation of GFM tables:
MyST converts this to:
This example comes from the getting started guide.
expectation
I would have expected:
This is the output of markdown-it-py, and the markdown-it live demo.
bug
Instead, the
<p>
tags are added, which means extra vertical spacing and odd content semantics.problem
I can’t think of a scenario where the extra vertical space, or the semantics, are desirable.
Reproduce the bug
List your environment