# Spaces and inline code formatting inconsistent behavior

**URL:** https://meta.discourse.org/t/spaces-and-inline-code-formatting-inconsistent-behavior/280206
**Category:** Bug
**Tags:** markdown
**Created:** [September 26, 2023, 7:36pm UTC](https://meta.discourse.org/t/spaces-and-inline-code-formatting-inconsistent-behavior/280206 "2023-09-26T19:36:08Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Canapin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/canapin/32/119591_2.png) [@Canapin](https://meta.discourse.org/u/Canapin)
#### Post date: [September 26, 2023, 7:36pm UTC](https://meta.discourse.org/t/spaces-and-inline-code-formatting-inconsistent-behavior/280206/1 "2023-09-26T19:36:08Z")

</div>

ℹ This is a Markdown bug, so I’m not sure anything can be done about it here… Still, just in case, here’s a topic.

If you have the following string:

backtick, formatted text, space, backtick, space, any character

The space **after** the closing backtick is trimmed, but a space appears **before** the closing backtick.

It is to be noted that markdown trims prepending and appending spaces in inline code formatting, which is its regular behavior:

A GIF will show the issue better than circumvoluted explanations:

![chrome_1QTL38fUj0](https://global.discourse-cdn.com/meta/original/4X/d/3/7/d378ab38142ace61667f641b8cae427746006334.gif)