The docs still seem to imply that restrict: 'E' is just a configurable default (rather than an enforced value). Maybe we should be more explicit about it being non-configurable (e.g. remove the default behavior like part).

LGTM otherwise.

OK, I'll improve the docs.

removing the ability to set the restrict option makes angular.component()'s unusable with the new ngComponentRouter until the router will support elements next to attributes ...

See #13603 and angular/angular#5278

@Mischi that is actually a problem with the router that needs to be fixed. @btford ?

Why remove element? How do you preserve DOM structure which is important for SEO?

@AIMMOTH not sure I understand what you mean.

@petebacondarwin Recommendations is that the DOM structure should be arranged for SEO. For instance <article></article> should be used. If this article is a component, it was possible to add the component as attribute <article component></article> but now you need to destroy DOM structure with <component></component>

Or have I missed something?