Non breaking space after strong causing rending to fail #146

Open
opened 2026-01-29 14:28:41 +00:00 by claunia · 0 comments
Owner

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: ``` <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> ```
claunia added the bug label 2026-01-29 14:28:41 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/markdig#146