I realize this thread is about influencing Mozilla to change their cookie behavior, and my only thought there is even if Mozilla changes their cookie behavior (extremely unlikely), there are other major browsers and your solution will still not work universally. You will need to find another way to accomplish what you're after within the confines of third-party cookie restrictions.
PayPal had the exact same problem and did the heavy lifting for everyone by open sourcing their solution. You can read about it here: https://medium.com/@bluepnume/introducing-paypals-open-source-cross-domain-javascript-suite-95f991b2731d For third-party cookies in particular, this describes how they do it using their open-source libraries: https://medium.com/@bluepnume/safaris-new-tracking-rules-and-enabling-cross-domain-data-storage-85241eea7483 Best wishes on your project, - Bil On Tue, Feb 12, 2019 at 7:55 PM OwN-3m-All <[email protected]> wrote: > I'm not handling payments though. That is all handled by PayPal in my > case. It doesn't matter what you're doing. Blocking 3rd party cookies > makes cross domain and cross origin widgets and applications break. And > there are a lot of good use cases for these... like in my case. A seller > can embed their store on their own web page, which is cross origin (and is > not something I manage or control). I handle all the processing, the end > user pays with PayPal, and the service gets notifications that payments > have been processed. It allows the seller to use my app anywhere on any > page. But with 3rd party cookies blocked, this is not possible. > > There needs to be a way to better handle this. I'd even go so far as > proposing that the end user not be allowed to block all 3rd party cookies. > Only those 3rd parties that are known to abuse the functionality... > > _______________________________________________ dev-privacy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-privacy
