Non breaking space after strong causing rending to fail #149

New Issue

claunia · 2026-01-29T14:28:44Z

claunia commented

2026-01-29 14:28:44 +00:00

Originally created by @topherdavis on GitHub (Oct 31, 2017).

The string contains a non-breaking space (character code 160) immediately after **time:** and this results in time: not being rendered in a strong tag.

Input:

**Check** **in/Check** **out:**  
**Check** **in** **time:** 5PM

Output:

<p><strong>Check</strong> <strong>in</strong> **time:** 5PM<br /><strong>Check</strong> <strong>out</strong> <strong>time:</strong> Flexible</p>

Expected output:

<p><strong>Check</strong> <strong>in</strong> <strong>time:</strong> 5PM<br /><strong>Check</strong> <strong>out</strong> <strong>time:</strong> Flexible</p>

Originally created by @topherdavis on GitHub (Oct 31, 2017). The string contains a non-breaking space (character code 160) immediately after `**time:**` and this results in `time:` not being rendered in a `strong` tag. Input: ``` **Check** **in/Check** **out:** **Check** **in** **time:** 5PM ``` Output: ``` Check in **time:** 5PM Check out time: Flexible ``` Expected output: ``` Check in time: 5PM Check out time: Flexible ```

claunia added the bug label 2026-01-29 14:28:44 +00:00

claunia closed this issue

2026-01-29 14:28:44 +00:00

claunia commented

2026-01-29 14:28:45 +00:00

@topherdavis commented on GitHub (Oct 31, 2017):

I was doing some more testing and this also causes a failure to render:

Input:

**Unlimited-Fun®**®

Output:

<p>**Unlimited-Fun®**®</p>

Expected:

<p><strong>Unlimited-Fun®</strong>®</p>

This also fails:

**Seats-**10B, 10A

So I'm not sure what type of characters make it fail.

Both of these also fail with em tags as well.

@topherdavis commented on GitHub (Oct 31, 2017): I was doing some more testing and this also causes a failure to render: Input: `**Unlimited-Fun®**®` Output: ``` **Unlimited-Fun®**® ``` Expected: ``` Unlimited-Fun®® ``` This also fails: ``` **Seats-**10B, 10A ``` So I'm not sure what type of characters make it fail. Both of these also fail with `em` tags as well.

claunia commented

2026-01-29 14:28:46 +00:00

@xoofx commented on GitHub (Oct 31, 2017):

Could you reproduce this on babelmark?

@xoofx commented on GitHub (Oct 31, 2017): Could you reproduce this on [babelmark](https://babelmark.github.io/)?

claunia commented

2026-01-29 14:28:46 +00:00

@topherdavis commented on GitHub (Oct 31, 2017):

Yes I verified all of them against babelmark and locally, but having trouble reproducing now. I'm going investigate a little more. Thanks!

@topherdavis commented on GitHub (Oct 31, 2017): Yes I verified all of them against babelmark and locally, but having trouble reproducing now. I'm going investigate a little more. Thanks!

claunia commented

2026-01-29 14:28:47 +00:00

@topherdavis commented on GitHub (Oct 31, 2017):

This isn't exactly the same as **Unlimited-Fun®**® but it is comparable.

https://babelmark.github.io/?text=Unlimited-Fun%26%23174%3B%26%23174%3B

@topherdavis commented on GitHub (Oct 31, 2017): This isn't exactly the same as `**Unlimited-Fun®**®` but it is comparable. https://babelmark.github.io/?text=*Unlimited-Fun%26%23174%3B*%26%23174%3B

claunia commented

2026-01-29 14:28:48 +00:00

@topherdavis commented on GitHub (Oct 31, 2017):

I knew I wasn't crazy. I must have either missed I was pasting the html encoded version or chrome was doing something awesome for me.

Again not the same as **Check** **in** **time:** 5PM

https://babelmark.github.io/?text=Check+in+time%3A%26%23160%3B5PM++%0A

@topherdavis commented on GitHub (Oct 31, 2017): I knew I wasn't crazy. I must have either missed I was pasting the html encoded version or chrome was doing something awesome for me. Again not the same as `**Check** **in** **time:** 5PM ` https://babelmark.github.io/?text=**Check**+**in**+**time%3A**%26%23160%3B5PM++%0A

claunia commented

2026-01-29 14:28:48 +00:00

@xoofx commented on GitHub (Nov 1, 2017):

Good, that's indeed a bug in Markdig.

@xoofx commented on GitHub (Nov 1, 2017): Good, that's indeed a bug in Markdig.

claunia commented

2026-01-29 14:28:49 +00:00

@xoofx commented on GitHub (Nov 1, 2017):

This should be part of upcoming 0.14.2

@xoofx commented on GitHub (Nov 1, 2017): This should be part of upcoming 0.14.2

claunia commented

2026-01-29 14:28:50 +00:00