Don't expect injecting table rows with ng-content to behave well in Google Chrome in an Angular 4 application.

Not if the table tag and the header are outside the ng-content. It works OK in IE, but in Google Chrome though something falls down and the width of a table cell will not be consistent in a row cell and header cell. The overall rules of the table with regards to what should be consistent widths are not enforced. I have noticed that Angular sprinkles its only HTML tags in the markup and then its JavaScript must somehow be explicitly ignoring these so that they do not behave like divs. Anyhow the stuff outside of the ng-content and the injected rows have some different inline settings in these funny tags I have noticed. I do not know if that is what is behind the Chrome gremlin.