OK That's fine!
I guess we should all distil our best ideas into the wishlist item? This issue is a classic example of something that appears as a bug to the user, but as a wishlist item to the developer :-)
Though I wish so, I'm not sure how much feasible is warning about silent 3rd party connection made by extensions.
The best way would allow the user to be aware to what sites an extension connects-to so the extension is limited to these sites alone.
But it is not unlikely that an extension might attempt connection to different sites at different times whereas the user might not approve/consent some of those sites.
Other than wishing for a possible solution to the above I would be fine to get all extensions to work (even if it means to allow extension to rely on DV-SSL connections)
If the the design is seemingly meant to notify (and let user choose if block) about DV-SSL then I wish the design will be consistently extended to extensions.
Though I feel difficult to generalize over what is not a bug considering this topic outline a loss of functionality (silent blocking of extensions using DV_SSL) over vanilla chromium.
Whereas vanilla chromium can be considered a legitimate reference, CD undoubtedly also provides new useful features and functionalities (eg DV-SSL notification for webpages).