ecore_evas: fix null selection set 37/312537/1 accepted/tizen/unified/20240612.100000 accepted/tizen/unified/dev/20240620.010648 accepted/tizen/unified/toolchain/20240624.121558 accepted/tizen/unified/x/20240612.110433 accepted/tizen/unified/x/asan/20240625.092706
authorBowon Ryu <bowon.ryu@samsung.com>
Tue, 11 Jun 2024 10:06:42 +0000 (19:06 +0900)
committerBowon Ryu <bowon.ryu@samsung.com>
Tue, 11 Jun 2024 10:06:42 +0000 (19:06 +0900)
commit091987b2d34b22fa99a30dd73a4897bc1f235fa4
tree46287ca45494c496999509ed87e90f7269bce068
parentce708389a0328df8a58e033f89c33eafa888ecc6
ecore_evas: fix null selection set

I think that the selection claim should fail when there is no available type.
But.. a null selection set is called from elm_object_cnp_selection_clear.
For compatibility, if a null selection set is invoked,
the selection data will be cleared and true will be returned.

Change-Id: I89d40578c051cf01847ca7b9994c90554b2939d5
Signed-off-by: Bowon Ryu <bowon.ryu@samsung.com>
src/modules/ecore_evas/engines/wayland/ecore_evas_wayland_common.c