projects / platform / upstream / elementary.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b03b284) | patch
atspi: not use destructed eo object 85/155785/1 accepted/tizen_3.0_common accepted/tizen_3.0_mobile accepted/tizen_3.0_tv accepted/tizen_3.0_wearable accepted/tizen/3.0/common/20171026.152903 accepted/tizen/3.0/mobile/20171026.010137 accepted/tizen/3.0/tv/20171026.010214 accepted/tizen/3.0/wearable/20171026.010238 submit/tizen_3.0/20171019.130042
authorShinwoo Kim <cinoo.kim@samsung.com>
Mon, 16 Oct 2017 06:58:56 +0000 (15:58 +0900)
committerShinwoo Kim <cinoo.kim@samsung.com>
Mon, 16 Oct 2017 06:58:56 +0000 (15:58 +0900)
commit7489b850cb1212c529bad70659036c9871783d1f
tree1f843681824fdab6c6543194c54f5c1256f37115tree | snapshot
parentb03b284f909c9f3b42f05c6ed2f5dae013b1acd7commit | diff
atspi: not use destructed eo object

It is possible to access destructed eo object using ATSPI interface.
The following sequence is possilbe, because AT-client such as screen-reader
does not know whether a widget object deleted or not.

1. _elm_radio_evas_object_smart_del
2. _elm_radio_elm_interface_atspi_accessible_state_set_get

So before using eo interface, we have to check if the eo object is vlid or
not using eo_destructed_is.

Change-Id: I7ffaf7bd905dcc2ef5770d9c1cef9de52ec77322
src/lib/elm_atspi_bridge.c diff | blob | history
Domain: UI Framework / EFL;