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
This is not a "real" bug, but merely an inconsistency.
SOUND gets an explicit VALUE=BINARY parameter upon serializing, when transformed from a v4.0 data:URI.
This is not the case for PHOTO and LOGO (cannot test KEY due to #678).
When parsing v3.0 with explicit VALUE=BINARY, this is preserved for all of PHOTO, LOGO, SOUND, and KEY.
When parsing v3.0 without explicit VALUE=BINARY, it is not added for PHOTO and LOGO (cannot test SOUND and KEY because of #676).
I suspect this is bug would also happen when parsing version 3.0 without explicit VALUE=BINARY.
I fear this bug may also be present with KEY (which I could not test).
The text was updated successfully, but these errors were encountered:
respiranto
changed the title
v3.0 serialization: SOUND gets explicit VALUE=BINARY (unlike PHOTO and LOGO)
vCard v3.0 serialization: SOUND gets explicit VALUE=BINARY (unlike PHOTO and LOGO)
Sep 24, 2024
Version: 4.5.5
This is not a "real" bug, but merely an inconsistency.
SOUND
gets an explicitVALUE=BINARY
parameter upon serializing, when transformed from a v4.0data:
URI
.This is not the case for
PHOTO
andLOGO
(cannot testKEY
due to #678).When parsing v3.0 with explicit
VALUE=BINARY
, this is preserved for all ofPHOTO
,LOGO
,SOUND
, andKEY
.When parsing v3.0 without explicit
VALUE=BINARY
, it is not added forPHOTO
andLOGO
(cannot testSOUND
andKEY
because of #676).I suspect this is bug would also happen when parsing version 3.0 without explicit
VALUE=BINARY
.I fear this bug may also be present with
KEY
(which I could not test).The text was updated successfully, but these errors were encountered: