Colors from xterm.js do not match colors in app

[tgb20]

Originally reported over Discord from powercas_gamer.

[tgb20]

I can't recreate it:

[powercasgamer]

Using this code in a Paper plugin

        getComponentLogger().error(
                MiniMessage.miniMessage().deserialize("<red>This is red</red> " +
                        "<red>This is also red!</red> " +
                        "<green>This is green</green> " +
                        "<white>And this is white</white>"
                ));
        getComponentLogger().info(
                MiniMessage.miniMessage().deserialize("<red>This is red</red> " +
                        "<red>This is also red!</red> " +
                        "<green>This is green</green> " +
                        "<white>And this is white</white>"
                ));
        getComponentLogger().warn(
                MiniMessage.miniMessage().deserialize("<red>This is red</red> " +
                        "<red>This is also red!</red> " +
                        "<green>This is green</green> " +
                        "<white>And this is white</white>"
                ));

I get this on the web panel:

And this on IOS:

/plugins shows it fine in green:

Another screenshot: ios:

web:

[tgb20]

I wrote my own plugin to recreate your messages. What is interesting is that the problem only occurs when using ANSIComponentSerializer. If the messages are sent as chat messages they render fine. This also lines up with the INFO tagged message as it doesn't get any special formatting.

I also noticed that on the web console the bold tag carries over to the message for ERROR and warning.

Actual ANSI being received by the console:

[00:50:01 ERROR]: This is red This is also red! This is green And this is white
[00:50:01 INFO]: This is red This is also red! This is green And this is white
[00:50:01 WARN]: This is red This is also red! This is green And this is white

I think this is an issue with the Swift xterm implementation so I am going to file an issue there. This seems the most likely as xterm.js seems to compensate for it somehow.

[tgb20]

This was fixed upstream. It will be included in a future release.