Why are you registering popper and tippy via unpkg.com? This is causing console.errors when developing offline.
Thanks for your feedback.
If you develop your site online, there are some benefits when using unpkg to load the file from global CDN. If you develop your site offline, you can download the file to the computer and replace the unpkg URL with your local URL.
As long as there is internet available, everything works, of course. I guess one could unregister your script and register them again using a local copy. Why is it beneficial to use a CDN? It's easy to violate GDPR this way, using mb front end submission. I would not do this, and suggest you include your dependencies locally. In my point of view, there is no harm in doing so.
Meta Box website, plugin and all extensions are 100% GDPR-compatible. (https://metabox.io/privacy-policy/)
This is not true, since you should ask for consent before IP addresses are transferred to third parties. I think no one cares if that happens on the backend of a content management system, but for the front end, it's another story.
So this is marked as resolved with the reason "some benefits" and that's it? What's about the unpkg usage on the front end and GDPR concerns?
Sorry for the late reply, there are so many tickets on our system for the past few days.
Using the unpkg link is not violate GDPR compliance if you have a notice that what data you collect from the user/visitor (what do you think about GDPR concern if you use Google Analytic link on your site?). Besides that unpkg is using Cloudflare to deliver the package via CDN and Cloudflare rule is very strict about GDPR compliance so you don't worry about that.
The purpose of using a CDN is to share the libs across extensions. Currently tooltip is used in the Tooltip and Builder extensions (backend). We'll move them to local in the next version.
Thanks, this is a reasonable explanation. So maybe bundling them with the meta box core plugin is a solution to get around this. I appreciate your decision to include it.
Currently tooltip is used in the Tooltip and Builder extensions (backend).
Backend is not 100% correct. As I wrote with mb front end submission, you can use this library on the front end, and therefore the reason I initially complained about GDPR compliance.