Closed EricPoul closed 2 years ago
I think it makes sense for sidebars to be below dialogs. Looks like another host is a reasonable solution. Perhaps we need to deprecate current sidebars and make a new implementation with this and customization in mind: https://github.com/TinkoffCreditSystems/taiga-ui/issues/553
I'd suggest keeping portal-host
for sidebars or custom(my own) similar stuff that creates children below dialogs and hosted-dropdown-host
that creates hosted-dropdown
s above dialogs and notifications and below tooltips.
And it's a little strange that host
creates children, not inside its template but after itself. It's just thoughts of improvements.
*below and above from end-user perspective
Renamed the issue to more general title. We have a low level API for portals, but we only use it for dropdowns and sidebars. Looks like a good idea would be to just add ability to make multiple portal hosts, put them inside tui-root with ngProjectAs and then use as people like, keeping dropdowns above everything else.
Custom portal hosts are now supported: https://github.com/Tinkoff/taiga-ui/pull/1485 https://taiga-ui.dev/portals
Which @taiga-ui/* package(s) are relevant/releated to the feature request?
No response
Description
There is a case when I'd like to open a dialog or show a notification while the sidebar or my custom portal is opened. Right now I can do this but
tui-dialog-host
andtui-notifications-host
are placed intui-portal-host
so that sidebar(custom portals) will be created over any dialogs or notifications.Suggestion:
Add an
ng-container
afterng-content
so we can add custom portals over main content but under dialogs, etc.read
ng-container
as ViewContainerRef; pass third(optional) argument to theaddComponentChild
;