3 ms·

Thanks. I'm not sure what exactly you mean by 'generic popup'. I'm assuming you are referring to overlaid div. I went with the iframe mainly to avoid having to

by bgdam 12y ago

Thanks. I'm not sure what exactly you mean by 'generic popup'. I'm assuming you are referring to overlaid div. I went with the iframe mainly to avoid having to provide CORS access to all the implementing sites. This way, it's always a same origin ajax/form post. Since this is just an MVP (I repurposed the site from an older project, the only thing new is the actual widget), the images are currently on a Linode VPN. When/If it gets popular, i'll be re-engineering this.

aakilfernandes 12y ago
I think you misunderstand CORS. You have to enable CORS on your server, not the sites that use your widget. http://stackoverflow.com/questions/298745/how-do-i-send-a-cross-domain-post-request-via-javascript/7605119#7605119 http://stackoverflow.com/questions/298745/how-do-i-send-a-cr...
- bgdam 12y ago
  Yeah, I know that. What I meant was that I did not want to set wildcards for the access-control-allow-origin header. If you use hostname reflection like in the linked stackoverflow example, issues arise when the widget is cached browser side by site A and then invoked by site B.
callumjones 12y ago
So they're not on a CDN as mentioned on the product page?
- bgdam 12y ago
  As of now, no they are not. If/when the widget takes off, I will start saving avatars to a CDN. I guess that makes it a bit dishonest to mention the CDN on the landing page, but since it will definitely be part of the standard package before I start charging, I let it slide.