[SalesForce] How to pass data attributes via lightning ui components with locker service active

This has a similar solution to this issue:

How to remove items from a dynamic list in Lightning component?

It doesn't feel clean, but this will return both the value and the input that called it:

Component

<div class="slds-form-element__control">
    <ui:inputPhone class="slds-input" placeholder="{!Phone}" change='c.save'>
    </ui:inputPhone>
    <span id="{!'thisInput'+i}"></span>
</div>

Controller

save: function(cmp, evt){
  var targetCmp = evt.getSource();
  var val = targetCmp.get('v.value');
  var inputId = targetCmp.getElement().nextSibling.nextSibling.id;

  console.log(value);
  console.log(inputId);
}

If you're wondering why the double "nextSibling", it's because the ui:input renders something like:

<!--render facet: 0000:00;a-->

following the element.

I do hope there is a better way to do this.

Too much for a comment but important to note:

Right now, there is a lot of noise. Other than the general rule it is hard to tell what is a bug, user error, or not allowed. I believe this is a consideration with the recent notification that the Enablement of Locker service this summer can now be rolled back by the admin rather than being permanent using API versioning

Received on 4-28-2017

In Summer '16, we introduced LockerService as a Critical Update. We planned to enable LockerService, including stricter Content Security Policy (CSP) in all orgs, starting with Summer '17. However, based on customer feedback, we have revised our rollout plan.

(Emphasis Mine)

With the revised rollout CSP has been decoupled from LockerService and won't be enforced in production orgs in Summer '17, and now you have the option disable LockerService by adjusting your API version.

LockerService Enforcement is Dependent on API Version LockerService is enabled for all Lightning components with API version 40.0 (the version for Summer '17) or higher. LockerService isn't enabled for components with API version 39.0 and lower, which covers any component created before Summer '17.

To enable LockerService for a component, set the API version to 40.0. You can disable LockerService for a component by setting the API version to 39.0 or lower for the component.

Component versioning enables you to associate a component with an API version. When you create a component, the default version is the latest API version. In Developer Console, click Bundle Version Settings in the right panel to set the component version.

Stricter CSP Restrictions Aren't Enforced Yet The stricter CSP restrictions, which mitigate the risk of cross-site scripting attacks, have been decoupled from LockerService and aren't enforced in production orgs in Summer '17. The stricter CSP changes are available only in sandboxes and Developer Edition orgs and can be activated in two new critical updates:

• Enable Stricter Content Security Policy for Lightning Components
• Enable Stricter Content Security Policy for Lightning Components in Communities This gives you more time to update your code to work with stricter CSP.