This has been showing up in various forms for some time and I think at least some aspect of it needs to be fixed since it causes compositor issues:
- Have image object
- Set pixels dirty, add update region
- Render occurs, image doesn't render because e.g., obj->cur->cache.clip.visible is false and evas_object_is_active() returns false
- User has no idea that image never rendered, image does not render
It seems to me that it's not the user's responsibility in this case to babysit evas and make sure that it eventually renders the image?