DefaultDomRenderer2 causing setAttribute not a function error on comment elements about angular HOT 4 OPEN

A ng-container will be rendered as a Comment Node in DOM and does not provide a setAttribute function.

You should use a div instead of ng-container or move the [attr.data-index] to a HTML Element.

from angular.

Please provide a runnable reproduction, or at least the stack trace in a non-optimized build. Without reproduction we are unable to provide any help.

from angular.

Marking it as a bug since this situation should be detected by a compiler and reported during the compilation time, without any runtime involvement. The attr. binding syntax clearly indicates that it is about binding to an attribute and we know that there are no attributes on the <ng-container> hence we can detect this situation statically.

from angular.

Please provide a runnable reproduction, or at least the stack trace in a non-optimized build. Without reproduction we are unable to provide any help.

I've managed to reproduce the bug on this small application https://github.com/magixian/applyzer (also added on main issue message).

In this process of reproducing the bug I seem to have figured out where the bug is coming from https://github.com/magixian/applyzer/blob/main/src/app/block-builder/block-builder.component.html#L2. This is an attribute which seem to not be required on our application so it can be removed without any issues. However, just to note that this was working all fine with the previous versions.

I will keep the issue open in the mean time just incase this case needs to be looked at.

from angular.