This issue only occured enlightenment.
Even if it is the same object tree, the problem may or may not occur depending on the order of objects being changed.
Therefore, it is difficult to make a sample or unit test.

checking dict->cset is useless in this code

this code makes the camera view to the full size.
please check one more time.

I modified evas code to fix this issue.
buniofh, if upstream git fix your problem, please let me know it.

for loop should check (sizeof(name)-1) .

@devilhorns
Hello~
I tested your patch and it work well in tizen mobile.
currently, this clipping code make big problem in tizen release.
this issue is one of the release breaker of tizen 3.0.
and we should fix this issue until end of August.

I heared the good news. you fix problem in wayland.
before release tizen 3.0, profiling team report some issue, wayland rendering cause more power consumtion than before(X backend)
they said it is because evas_render update inter funtion, clip all the area code. but I troubled find solution, but I heared that you are doing it now.
I really HAPPY!!!!!!!!!!!!!!!!!!
i'll test that your patch solve our problem. thank you~~~

currently evas keygrab have hole related with exclusive.
if there are object already grab key, it can deal with keygrab propery between object.
this patch can be added