remark-parse: ( in strong block will broke the block

[ZxBing0066]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions

remark-parse: ^9|^10

Link to runnable example

No response

Steps to reproduce

https://codesandbox.io/s/remark-parser-strong-bug-1-yggwkm?file=/src/styles.css

**aaa(**123 will be parse to a paragraph without children which should be a paragraph with a strong children.

Expected behavior

It should be a strong block, this is broken with version 9 or 10, but works fine with version 8.

https://codesandbox.io/s/remark-parser-strong-bug-2-tlc8dd?file=/src/styles.css

Actual behavior

Runtime

No response

Package manager

No response

OS

No response

Build and bundle tools

No response

[ChristianMurphy]

Welcome @ZxBing0066! 👋

This is a duplicate of #917

To quote the answer from there

A left-flanking delimiter run is a delimiter run that is (1) not followed by Unicode whitespace, and either (2a) not followed by a Unicode punctuation character, or (2b) followed by a Unicode punctuation character and preceded by Unicode whitespace or a Unicode punctuation character. For purposes of this definition, the beginning and the end of the line count as Unicode whitespace.

And closing strong text

A right-flanking delimiter run is a delimiter run that is (1) not preceded by Unicode whitespace, and either (2a) not preceded by a Unicode punctuation character, or (2b) preceded by a Unicode punctuation character and followed by Unicode whitespace or a Unicode punctuation character. For purposes of this definition, the beginning and the end of the line count as Unicode whitespace.

(https://spec.commonmark.org/0.30/#emphasis-and-strong-emphasis)

Don't seem to be met.

I'm not sure the HTML 1<strong>(abc)</strong>2 can be represented precisely/exactly in markdown.

A close equivalent may be adding zero width space characters between 1 and ** as well as ** and 2. 🤔

To answer your other comment

It should be a strong block, this is broken with version 9 or 10, but works fine with version 8.

remark 8 had a bug not implementing CommonMark correctly, that has been addressed in later versions and will remain fixed.

[github-actions]

Hi! Thanks for taking the time to contribute!

Because we treat issues as our backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn’t an exact duplicate but is closely related.

Thanks,
— bb

[github-actions]

Hi team! It seems this post is a duplicate, but hasn’t been marked as such. Please post a comment w/ Duplicate of #123(no final .) to do so. See GH docs for more info.

Thanks,
— bb

[ZxBing0066]

Hi @ChristianMurphy,

Thanks for you response, that's very helpful. However the current behavior still makes me confusing. If that is by design, I think **aaa\(**123 should be working since the punctuation character has been escaped. Just my own option.

[ChristianMurphy]

In CommonMark **aaa\(**123 is not strong text either https://spec.commonmark.org/dingus/?text=**aaa%5C(**123
same in GitHub Flavored Markdown (GFM), **aaa\(**123 renders as **aaa(**123

[ZxBing0066]

OK, you are right. Thanks for your patient answer~😌