PortalOutlet using existing component instance as the host

[habibialkaff]

Please describe the feature you would like to request.

PortalOutlet where the "outletElement" is an instance of an existing component

What is the use-case or motivation for this proposal?

I'm using Portal to render an overlay on top of an existing component (host component).

Is there anything else we should know?

Currently the way I do it is to have the host component injects the ElementRef so that I can get the nativeElement which I can use it as the outletElement when instantiating the DOMPortalOutlet.

I wish CDK provides a way where I don't need to explicitly injects ElementRef just so that I can get access to the host Element

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.