{"action":"created","issue":{"url":"https://api.github.com/repos/braintree/braintree-web/issues/29","labels_url":"https://api.github.com/repos/braintree/braintree-web/issues/29/labels{/name}","comments_url":"https://api.github.com/repos/braintree/braintree-web/issues/29/comments","events_url":"https://api.github.com/repos/braintree/braintree-web/issues/29/events","html_url":"https://github.com/braintree/braintree-web/issues/29","id":60005529,"number":29,"title":"Talk about features that would help Single Page Apps","user":{"login":"jeffcarp","id":916028,"avatar_url":"https://avatars.githubusercontent.com/u/916028?v=3","gravatar_id":"","url":"https://api.github.com/users/jeffcarp","html_url":"https://github.com/jeffcarp","followers_url":"https://api.github.com/users/jeffcarp/followers","following_url":"https://api.github.com/users/jeffcarp/following{/other_user}","gists_url":"https://api.github.com/users/jeffcarp/gists{/gist_id}","starred_url":"https://api.github.com/users/jeffcarp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeffcarp/subscriptions","organizations_url":"https://api.github.com/users/jeffcarp/orgs","repos_url":"https://api.github.com/users/jeffcarp/repos","events_url":"https://api.github.com/users/jeffcarp/events{/privacy}","received_events_url":"https://api.github.com/users/jeffcarp/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":23,"created_at":"2015-03-05T19:48:23Z","updated_at":"2015-06-29T22:47:57Z","closed_at":null,"body":"`braintree-web`'s design comes from a time when checkout flows generally used a `<form>` POST. This is no longer the case in 2015, where SPAs and JS-heavy checkout flows are common.\r\n\r\nThere are a couple things that keep `braintree-web` from working well in SPAs, the biggest of which is that `braintree.setup` can only be called once per page load.\r\n\r\nI'm starting this thread to discuss what kinds of features would be useful for making `braintree-web` work better in JS-heavy checkout flows.\r\n\r\nRelated Issues:\r\n\r\n- setup() with different user #18\r\n- Ability to disable dropin form event handlers #4\r\n- paymentMethodNonceReceived callback doesn't get a new nonce after submitting and re-entering number #20\r\n- paypal support? https://github.com/jeffcarp/braintree-angular/issues/8"},"comment":{"url":"https://api.github.com/repos/braintree/braintree-web/issues/comments/116873114","html_url":"https://github.com/braintree/braintree-web/issues/29#issuecomment-116873114","issue_url":"https://api.github.com/repos/braintree/braintree-web/issues/29","id":116873114,"user":{"login":"paulrnash","id":1303337,"avatar_url":"https://avatars.githubusercontent.com/u/1303337?v=3","gravatar_id":"","url":"https://api.github.com/users/paulrnash","html_url":"https://github.com/paulrnash","followers_url":"https://api.github.com/users/paulrnash/followers","following_url":"https://api.github.com/users/paulrnash/following{/other_user}","gists_url":"https://api.github.com/users/paulrnash/gists{/gist_id}","starred_url":"https://api.github.com/users/paulrnash/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paulrnash/subscriptions","organizations_url":"https://api.github.com/users/paulrnash/orgs","repos_url":"https://api.github.com/users/paulrnash/repos","events_url":"https://api.github.com/users/paulrnash/events{/privacy}","received_events_url":"https://api.github.com/users/paulrnash/received_events","type":"User","site_admin":false},"created_at":"2015-06-29T22:47:57Z","updated_at":"2015-06-29T22:47:57Z","body":"Pretty much what he said. I've wasted hours and hours trying to make\nsomething reasonable out of this technology. It doesn't seem like either\nthe default web integration or hosted fields will work for anything but a\nmultiple page click through experience. After earlier experiences where\nbraintree's support had been impeccably good, I am now finding that it is\nnot so responsive and technically they are not keeping up with the times.\nPerhaps all the PayPal and eBay split noise is affecting the focus of the\nteam or confusing the priorities. I am seriously considering switching to a\ncompetitor after my experience dealing with this mess, particularly sense\nthe communication from Braintree has mostly been either radio silence or\n\"uh sorry.\" they don't even seem to be aware of the reason this is such an\ninconvenience.\nOn Jun 29, 2015 3:01 PM, \"tastyeggs\" <notifications@github.com> wrote:\n\n> +1\n>\n> Come on braintree, get your act together. Come live in the future with us.\n> Everyone is designing single-page applications and it is extremely\n> frustrating when we have to integrate with libraries designed by companies\n> who think they use the latest tech, but actually have no clue.\n>\n> This is CS 101 fundamentals; make your code self-contained; make it leave\n> no trace on the system its running on. We thought we should use braintree\n> because it would be easier to integrate, but it's taking the same amount to\n> time, and same amount of nasty hacks as it takes to integrate with your\n> parent company.\n>\n> You sitting on this issue for 3 months shows that you either don't care\n> about your users experience, or you have no clue what single-page\n> applications are about, hence don't see how badly you're crippling the\n> experience of our users and developers. Either way, it reflects poorly on\n> your company.\n>\n> Forgive my strong language; but this is *exactly* how I feel. If this\n> were an open-source library, I would have fixed this by now. But now we're\n> all trapped to writing shitty code, because either you guys don't care, or\n> you guys just don't get it.\n>\n> Wake up!!\n>\n> —\n> Reply to this email directly or view it on GitHub\n> <https://github.com/braintree/braintree-web/issues/29#issuecomment-116859911>\n> .\n>\n"}}