You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm observing that colour_to_integer() is casting "transparent" to an opaque color equivalent to "white" (with a message saying unknown color) and is casting NA_character_ to "#00000000" which is a fully transparent value but a slightly different fully transparent value from what col2rgb() assigns to it. I'd pedantically "expect" colour_to_integer(NA_character_) to instead return 16777215L (the same as colour_to_integer("#FFFFFF00")).
My understanding is that some graphic devices or image viewers don't support alpha transparency so this would be the difference between a "transparent" background being rendered "white" or "black" in such devices/programs...
I'm observing that
colour_to_integer()
is casting "transparent" to an opaque color equivalent to "white" (with a message saying unknown color) and is castingNA_character_
to "#00000000" which is a fully transparent value but a slightly different fully transparent value from whatcol2rgb()
assigns to it. I'd pedantically "expect"colour_to_integer(NA_character_)
to instead return16777215L
(the same ascolour_to_integer("#FFFFFF00")
).I've observed that
farver::encode_native()
also has trouble with these two edge cases: thomasp85/farver#47The text was updated successfully, but these errors were encountered: