Container input support

[braintree]

Container input support

[crookedneighbor]

This was released in version 1.1.0

[crookedneighbor]

We decided not to support it in order to simplify the API.

Can you explain why your integration depends on it? Does the element not have an id property you can leverage? IE:

braintree.dropin.create({
  authorization: auth,
  selector: '#' + myDomNode.id
}, callback);

[buu700]

We're using Braintree in an Angular component, so the most obvious way to access the intended DOM node is as a descendant of the root of the component.

Although, now that I think about it, while it's a bit of a hack, we can just generate a random GUID and set it as the ID to use for the selector.