Fix #342 without expanding API

[akiran]

@AntJanus,
when data-src is dynamically updated, angular is updating the src attribute value

So setting data-src value with src value is fixing #342 without introducing new attribute.
I tested the below example with this fix and it is working fine.

<ul ng-init="items=['assets/img/iconic/action.svg', 'assets/img/iconic/ban.svg', 'assets/img/iconic/bell.svg']">
  <li ng-repeat="item in items" >
  <img zf-iconic="" data-src={{item}} class="iconic-sm" >
  </li >
</ul>

[AntJanus]

@akiran I don't understand. You're using the src attribute to be applied to data-src but in your example you're only using data-src.

Either way, I think it'd make sense to have a dyn-src that you can send a variable to without having to use {{ }} inside an attribute (something I'm not a fan of). But to make sure we can cover as many developers as possible, I'd like to have both.

Can you change the file to not delete the dyn-src but keep your fix as well?

[akiran]

If we pass an expression to data-src, angular evaluates it and pass its value to src (Similar to ng-src).

Developers can pass a path or path expression to data-src with this fix.

<img zf-iconic="" data-src="iconic/thumb.svg " class="iconic-sm" >
<img zf-iconic="" data-src="iconic/{{name}}.svg"  class="iconic-sm" >

Angular evaluates data-src and pass it to src.
In the directive, src value is again set to data-src because iconic.js uses the value on data-src attribute.

[akiran]

Added back dynSrc option