offset attribute conflict (since 0.11.0)

[Sayene]

ng-attr-offset is ignored when using md-material builds 0.11.1 and current master
Here is rendered html example with svg gradient, where other (here: stop-color) ng-attr- are evaluated but ng-attr-offset is ignored:

<linearGradient x1="100%" y1="100%" x2="100%" y2="0%" id="hpp-gradient">
            <stop ng-attr-offset="0%" ng-attr-stop-color="{{fill}}" stop-color="#93CE8C"></stop>
            <stop ng-attr-offset="{{(complete)?complete:0}}" ng-attr-stop-color="{{fill2}}" stop-color="white></stop>
</linearGradient>

This was working ok in 10.0.1.

[Sayene]

UPDATE: actually this is not only ng-attr-offset that is ignored (REMOVED) but all attributes "offset", no matter where used, are now removed... this is effect of line 2869:

      .directive('offset'              , attributeWithObserve('offset')              )

and makes e.g. using SVG and gradients not possible. Should 'offset' attribute used by md be renamed?

[ThomasBurleson]

@jelbourn, @robertmesserle - what are your thoughts here?

• Is this a conflict with a common attribute offset ?
• Should we rename the attribute to be flex-offset to be aligned with flex-order ?
• I think this solution is probably best...

[jelbourn]

Perhaps layout-offset, since it doesn't actually have anything to do with flex?