Thank you for pointing this out.

You're correct that the current behavior may seem counterintuitive without more context. However, terms like RGBA and BGRA are inherently ambiguous unless paired with a clear definition of:

• Bit significance (which channel is in which bit position of the uint32_t)
• Endianness (how those bits are laid out in memory)

For example, in a little-endian system (like x86/x64), a uint32_t value such as 0xFF0000FF will be laid out in memory as [0xFF, 0x00, 0x00, 0xFF], which is BGRA in memory but ABGR in bits.

Our current implementation originates probably from WPF or DirectX.

You're absolutely right that it would be possible to redefine the packing convention. However, doing so now would risk breaking existing integrations that already rely on the current behavior. For that reason, we consider this behavior legacy but stable.

I didn't have the context, indeed I understand that you don't want to change that now. Sorry about that!

Always, thanks for your valuable feedback!