igniteui-angular
igniteui-angular copied to clipboard
Overlay doesn't calculate its position fit based on the outlet but based on the document
Description
Describe the issue.
- igniteui-angular version: 10.2.x
- browser: any
Steps to reproduce
- The viewport fit calculation is based on the document instead of the provided outlet thus resulting in strange behavior sometimes:

can be useful in cases like this one:

Provide a way to choose whether to make the calculations based on the outlet or the document.
This is a feature request. We should add option to overlay determining whether or not overlay content should be shown always in the outlet, e.g. showInOutlet.
Note this strongly contradicts with all connected position strategies. This is why we should very carefully decide what should happen in any target - outlet configuration. The most easy one is outlet with target inside it. The most strange one coming to my mind will be target next to the outlet.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
There has been no recent activity and this issue has been marked inactive.
Using ContainerPositionStrategy should solve this issue.