Embeds can't be individually removed

(#441) Bug Awaiting confirmation embeds

Summary

The Fluxer client shows an "X" for each embed, but clicking one of them removes all embeds instead of only the selected one. There should either be only one "X" or the functionality to remove individual embeds should be added.

Steps to reproduce

  1. Send a webhook message with two embeds.
  2. (Requires permissions) Click on one of the "X" next to the embeds in the message.
  3. Both embeds will be removed even though only one "X" was clicked.

Environment (optional)

stable build 160 (7541d2c), 2026-03-22 03:35:25 UTC, Chrome 144.0.0.0, Linux (x86)

Logs or screenshots (optional)

The two "X": image The message after clicking one of the "X": image
  • 567420504-55413323-a976-4cd7-ba67-6bb2c1db1126.png

    567420504-55413323-a976-4cd7-ba67-6bb2c1db1126.png

    393×179 | 13 kB

  • 567420583-30b630d4-f666-433c-a927-74c4dddb055e.png

    567420583-30b630d4-f666-433c-a927-74c4dddb055e.png

    378×95 | 9 kB

5 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Fixed to Awaiting confirmation
This was closed in a bulk cleanup before Fluxer V2 without being checked or fixed. It may work now, so it is waiting for someone to confirm whether the bug still happens.
Comment by @PilkeySEK
RexSystem 1 vote originally by @PilkeySEK on GitHub OP
From looking at network requests, this is because the client just sends an "edit message" request with the SUPPRESS_EMBEDS flag applied, regardless of how many embeds there are (resulting in all embeds being suppressed).
Comment by @UnknownLITE
RexSystem 1 vote originally by @UnknownLITE on GitHub
Same behavior as Discord. But a option to individually suppress embeds would be great.
Comment by @TheKodeToad
RexSystem 1 vote originally by @TheKodeToad on GitHub
How would only deleting some embeds even work API wise? maybe DELETE /chanels/xxx/messages/xxx/embeds/0 ?
Comment by @PilkeySEK
RexSystem 1 vote originally by @PilkeySEK on GitHub OP
I mean, embeds have a specific order that is the same on all clients, so an index would probably be the easiest solution, yes