pgilad/angular-html5

Change your ng-attributes to data-ng-attributes for html5 validation

angular-html5's Issues

<ng-transclude> tag becomes <data-ng-transclude>

The <ng-transclude> tag becomes <data-ng-transclude>. It doesn't break functionality, but its an unexpected and undesireable effect.

Is it possible to add support to restrict replacement within the "class" attribute"?

When angular-html5 is configured to replace custom prefixes, e.g. 'my-', and running the replace method on code such as <div my-tab class="my-tab" > results in <div data-my-tab class="data-my-tab" />.

Can the module be restricted/configured so that it doesn't do replacement within attribute values, but only attribute names?

Conversion to HTML5 self-closing tags breaks browser SVG parsing

I'm using gulp-angular-htmlify in my build process, and just found it to be at the root an issue with broken SVG rendering. The symptom is that any SVG elements in my HTML document that contain more than one child element (e.g., multiple <path>s) are only rendering the first child element. When I view the generated source, I notice that the browser has interpreted them as nested elements:

<svg>
  <path>
    <path>
      <path>
</svg>

It appears that the gulp-angular-htmlify output tries to convert any XHTML-style self-closing tags (e.g., <path/>) to their HTML5 equivalent (e.g., <path>). However, in the case of SVG or MathML elements included in HTML documents, this is against the spec:

http://www.w3.org/TR/html-markup/syntax.html#svg-mathml

Those elements must preserve the self-closing slash to be parsed correctly by browsers (at least the latest Chrome/Mac, where I've seen this issue). Removing the gulp-angular-htmlify step from my Gulpfile fixed the problem immediately.

I've only had a brief chance to look at the source code - could this have something to do with parsing via cheerio?

improve and sort readme

add cli