Preserve attributes camelcased

[Mouvedia]

cf http://stackoverflow.com/questions/24910730/how-to-handle-patterntransform-using-ng-attr-keep-it-camelcased

In short Id like ng-attr-patternTransform to produce patternTransform (instead of patterntransform currently).
It's a common problem if you are dealing with svg elements.

The viewBox attribute is another common case.

[caitp]

this is a reasonable request, I think. The thing is that it makes it really hard to normalize the attribute name.

[caitp]

I don't think it should break any apps though, it's just another step towards "first class SVG elements", and HTML attributes are case insensitive anyways, so it should be okay.

[Mouvedia]

Looking at this page, it makes you realize how many attributes are affected.

[wesleycho]

One solution could be to store a hash of attributes with key-value pairs being [svg attribute lowercase]: [svg attribute correct cased], and to check if the string is prefixed against that hash. If the value is defined, then the casing could be preserved - it seems that whenever ng-attr is present, the browser interprets it as a regular HTML attribute and thus reads it as a case insensitive name.

Here is a simple plunker that outputs the object you can use to inspect with: http://plnkr.co/edit/sn2IsH0d9fP0jbK7VP4X?p=preview .

The attributes object on the DOM node can be used to find the case insensitive version of the attribute.

[IgorMinar]

as discussed, we can just have an encoding scheme for ngAttr and use for example underscore to denote camelcasing.

so ng-attr-pattern_transform="foo" would create a binding for patternTransform attribute.