https://bugs.documentfoundation.org/show_bug.cgi?id=103673
--- Comment #2 from Pranav Kant <[email protected]> ---
(In reply to Aleksander Machniak from comment #1)
> I guess this is java color specification. I found how to convert it to hex
> in javascript:
These are RGB integer values directly fed to loleaflet by LO core.
>
> color = ((color)>>>0).toString(16).slice(-6);
> color = '#' + ("000000").substring(0, 6 - color.length) + color;
>
> I'm not 100% sure this is correct.
Yes, that is the correct way to convert. We convert it similarly in loleaflet
too.
> Still, the color is different than the td.usercolor (which is black).
The color is explicitly set to black in case of current user, overwriting the
value that you noticed in View_Added message so that it matches with the user's
cursor which is black. LO core assigns each author a separate color and the
value that you get in View_Added message is this same value. This is used in
Change Tracking UI (coming soon ...), and comments. You can notice that the
background color of comment box is same as of this value. Don't think would be
a good idea to overwrite this value with black for current user as we/you might
need it in future, but maybe we can add another postmessage API that let you
know the viewid of the current user (?) [or maybe integrate the same in those
editor init. message ?]
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
