AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Edit history

Earlier versions of Code block parsing is less forgiving than Discord about whitespace around the fences, newest first.

Current version | Edited by Rex
Changes
Already posted in summary.Removed: ### ChecksRemoved: Removed: - ☑ I searched existing issues.Removed: - ☑ I wrote this report in my own words, except for direct translation if needed.Removed:
Show

Code block parsing is less forgiving than Discord about whitespace around the fences

Summary

Fluxer does not render text inside code blocks correctly in most cases where there's no whitespace after the close mark, resulting in bad rendering, for example, as shown in the image: image The expected behaviour is for a single "Text" line to be rendered before, inside, and after the code block. Amount of spacing around the code block may differ (as is the case on Discord), but I'd expect the text itself to render as described. NOTE: This is a repost of #138 with updated screenshots - I can still reproduce the issue (including all the test results listed below) after the Fluxer V2 release, though the code block part is now no longer rendered as a code block at all (i.e. it's rendered exactly as written, with no formatting).

Steps to reproduce

  1. Send a message with the following content:
    Text```
Text
```Text
  2. See the issue (as seen in the image above; note: in some failing variations, the code block may render differently from the screenshot, but still not in the expected way).
Below you can find a complete list of all 16 variations of the following variables:
  • Whitespace before open
  • Whitespace after open
  • Whitespace before close
  • Whitespace after close
8 out of 16 renders correctly on Fluxer. 16 out of 16 renders correctly on Discord. "renders correctly" means it gives the expected behaviour, as described in the previous section. Test results for all 16 combinations.
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text```Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text```
Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```
Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```
Text
```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```
Text
```
Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text
```Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text
```
Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```
Text```
Text
  1. ❌ Does not work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```
Text
```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```
Text
```
Text

Environment

Canary Web 2026.605.11941, Linux (x86), Chrome 149.0.0.0, Locale en-US

Logs or screenshots

Already posted in summary.
Edited by Rex
Changes
Removed: Code blocking parsing is less forgiving about whitespace around open/close marks compared to DiscordAdded: Code block parsing is less forgiving than Discord about whitespace around the fences### Summary
Show

Code block parsing is less forgiving than Discord about whitespace around the fences

Summary

Fluxer does not render text inside code blocks correctly in most cases where there's no whitespace after the close mark, resulting in bad rendering, for example, as shown in the image: image The expected behaviour is for a single "Text" line to be rendered before, inside, and after the code block. Amount of spacing around the code block may differ (as is the case on Discord), but I'd expect the text itself to render as described. NOTE: This is a repost of #138 with updated screenshots - I can still reproduce the issue (including all the test results listed below) after the Fluxer V2 release, though the code block part is now no longer rendered as a code block at all (i.e. it's rendered exactly as written, with no formatting).

Steps to reproduce

  1. Send a message with the following content:
    Text```
Text
```Text
  2. See the issue (as seen in the image above; note: in some failing variations, the code block may render differently from the screenshot, but still not in the expected way).
Below you can find a complete list of all 16 variations of the following variables:
  • Whitespace before open
  • Whitespace after open
  • Whitespace before close
  • Whitespace after close
8 out of 16 renders correctly on Fluxer. 16 out of 16 renders correctly on Discord. "renders correctly" means it gives the expected behaviour, as described in the previous section. Test results for all 16 combinations.
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text```Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text```
Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```
Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```
Text
```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```
Text
```
Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text
```Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text
```
Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```
Text```
Text
  1. ❌ Does not work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```
Text
```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```
Text
```
Text

Environment

Canary Web 2026.605.11941, Linux (x86), Chrome 149.0.0.0, Locale en-US

Logs or screenshots

Already posted in summary.

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.
Edited by Rex
Changes
**The expected behaviour** is for a single "Text" line to be rendered before, inside, and after the code block. Amount of spacing around the code block may differ (as is the case on Discord), but I'd expect the text itself to render as described.Removed: NOTE: This is a repost of [#224](https://feedback.fluxer.com/p/138) with updated screenshots - I can still reproduce the issue (including all the test results listed below) after the Fluxer V2 release, though the code block part is now no longer rendered as a code block at all (i.e. it's rendered exactly as written, with no formatting).Added: NOTE: This is a repost of [#138](https://feedback.fluxer.com/p/138) with updated screenshots - I can still reproduce the issue (including all the test results listed below) after the Fluxer V2 release, though the code block part is now no longer rendered as a code block at all (i.e. it's rendered exactly as written, with no formatting).### Steps to reproduce
Show

Code blocking parsing is less forgiving about whitespace around open/close marks compared to Discord

Summary

Fluxer does not render text inside code blocks correctly in most cases where there's no whitespace after the close mark, resulting in bad rendering, for example, as shown in the image: image The expected behaviour is for a single "Text" line to be rendered before, inside, and after the code block. Amount of spacing around the code block may differ (as is the case on Discord), but I'd expect the text itself to render as described. NOTE: This is a repost of #138 with updated screenshots - I can still reproduce the issue (including all the test results listed below) after the Fluxer V2 release, though the code block part is now no longer rendered as a code block at all (i.e. it's rendered exactly as written, with no formatting).

Steps to reproduce

  1. Send a message with the following content:
    Text```
Text
```Text
  2. See the issue (as seen in the image above; note: in some failing variations, the code block may render differently from the screenshot, but still not in the expected way).
Below you can find a complete list of all 16 variations of the following variables:
  • Whitespace before open
  • Whitespace after open
  • Whitespace before close
  • Whitespace after close
8 out of 16 renders correctly on Fluxer. 16 out of 16 renders correctly on Discord. "renders correctly" means it gives the expected behaviour, as described in the previous section. Test results for all 16 combinations.
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text```Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text```
Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```
Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```
Text
```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```
Text
```
Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text
```Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text
```
Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```
Text```
Text
  1. ❌ Does not work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```
Text
```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```
Text
```
Text

Environment

Canary Web 2026.605.11941, Linux (x86), Chrome 149.0.0.0, Locale en-US

Logs or screenshots

Already posted in summary.

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.
Original by Rex
Show

Code blocking parsing is less forgiving about whitespace around open/close marks compared to Discord

Summary

Fluxer does not render text inside code blocks correctly in most cases where there's no whitespace after the close mark, resulting in bad rendering, for example, as shown in the image: image The expected behaviour is for a single "Text" line to be rendered before, inside, and after the code block. Amount of spacing around the code block may differ (as is the case on Discord), but I'd expect the text itself to render as described. NOTE: This is a repost of #224 with updated screenshots - I can still reproduce the issue (including all the test results listed below) after the Fluxer V2 release, though the code block part is now no longer rendered as a code block at all (i.e. it's rendered exactly as written, with no formatting).

Steps to reproduce

  1. Send a message with the following content:
    Text```
Text
```Text
  2. See the issue (as seen in the image above; note: in some failing variations, the code block may render differently from the screenshot, but still not in the expected way).
Below you can find a complete list of all 16 variations of the following variables:
  • Whitespace before open
  • Whitespace after open
  • Whitespace before close
  • Whitespace after close
8 out of 16 renders correctly on Fluxer. 16 out of 16 renders correctly on Discord. "renders correctly" means it gives the expected behaviour, as described in the previous section. Test results for all 16 combinations.
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text```Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text```
Text```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text```
Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text```
Text
```Text
  1. ✅ Works
    • Whitespace before open: No
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text```
Text
```
Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: No
Text
```Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```Text```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```Text
```Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: No
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```Text
```
Text
  1. ❌ Does NOT work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: No
Text
```
Text```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: No
    • Whitespace after close: Yes
Text
```
Text```
Text
  1. ❌ Does not work
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: No
Text
```
Text
```Text
  1. ✅ Works
    • Whitespace before open: Yes
    • Whitespace after open: Yes
    • Whitespace before close: Yes
    • Whitespace after close: Yes
Text
```
Text
```
Text

Environment

Canary Web 2026.605.11941, Linux (x86), Chrome 149.0.0.0, Locale en-US

Logs or screenshots

Already posted in summary.

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.