Drop Target Area definition in DamMediaSource should provide more control for activation and deactivation on the component level
Currently the DamMediaSource enables drop area on components containing media elements, like images. in some cases, when a component contains subcomponents with media elements it causes problems when dropping a media element from the content finder on the first subcomponent. The image data is not posted to the subcomponent resource, but to the parent component, overriding the resource type, which makes the component unusable
it would be helpful, if the media handling would provide some control options over the drop area definition.
implement a first solution - please review/test
MediaArgs provides a new property "dragDropSupport" which gives more control, default ist "AUTO" which compares the current resource path with the resource for which the media handling is applied.