AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Edit history

Earlier versions of Embed field values can overlap/overflow with some types of markdown, newest first.

Current version | Edited by Rex
Changes
stable (5b0afb2), 2026-02-21 14:40:38 UTC, Electron 39.2.7, Linux 5.15.0-170-generic (x64), desktop stable 0.0.8Removed: ### Logs or screenshots (optional)Removed: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched for existing issues and didn't find a duplicate.Removed:
Show

Embed field values can overlap/overflow with some types of markdown

Summary

Embed field values overlap sometimes: image image

Steps to reproduce

For timestamps:
  1. Create a message with the following request:
    {
  "embeds": [
    {
      "fields": [
        {
          "inline": true,
          "name": "Test",
          "value": "<t:1771792416>"
        },
        {
          "inline": true,
          "name": "Test",
          "value": "<t:1771792416>"
        },
        {
          "inline": true,
          "name": "Test",
          "value": "<t:1771792416>"
        }
      ]
    }
  ]
}
  2. See the issue.
For roles:
  1. Create a role named "VERY LONG ROLE NAME TESTING".
  2. Create an embed with 3 inline fields as shown above. Replace the "value" keys with a mention of a role created in the previous step.
  3. See the issue

Environment (optional)

stable (5b0afb2), 2026-02-21 14:40:38 UTC, Electron 39.2.7, Linux 5.15.0-170-generic (x64), desktop stable 0.0.8
Original by Rex
Show

Embed field values can overlap/overflow with some types of markdown

Summary

Embed field values overlap sometimes: image image

Steps to reproduce

For timestamps:
  1. Create a message with the following request:
    {
  "embeds": [
    {
      "fields": [
        {
          "inline": true,
          "name": "Test",
          "value": "<t:1771792416>"
        },
        {
          "inline": true,
          "name": "Test",
          "value": "<t:1771792416>"
        },
        {
          "inline": true,
          "name": "Test",
          "value": "<t:1771792416>"
        }
      ]
    }
  ]
}
  2. See the issue.
For roles:
  1. Create a role named "VERY LONG ROLE NAME TESTING".
  2. Create an embed with 3 inline fields as shown above. Replace the "value" keys with a mention of a role created in the previous step.
  3. See the issue

Environment (optional)

stable (5b0afb2), 2026-02-21 14:40:38 UTC, Electron 39.2.7, Linux 5.15.0-170-generic (x64), desktop stable 0.0.8

Logs or screenshots (optional)

No response

Checks

  • ☑ I searched for existing issues and didn't find a duplicate.