A modern programming language that makes developers happier.

kotlinlang

Hey all, I'm currently dealing with a little "bug". I'm using `Scaffold` and consuming top bars and bottom bars + window insets as `contentPadding` inside the scrollable container (`ScrollColumn`/`LazyColumn`/ etc) in the `content` slot. The bars are semi-translucent or solid, depending on screen style. If the scrollable container contains multiple input fields that may be outside of the viewable bounds, the global focus requester will try to bring the element into view. When doing that, it will take the whole scrollable container bounds and not the "interactable" bounds (as some areas to the top and bottom will be partially or fully obstructed).

The obvious fix is to bring is to apply insets and top/bottom bounds as padding instead of contentPadding, but then we miss out on having parallax/translucency. I've checked `BringIntoViewModifierNode` and `bringIntoViewResponder`, but not sure how this helps the cause. TIA!

<https://github.com/compose-fluent/compose-fluent-ui/blob/dev/fluent%2Fsrc%2FcommonMain%2Fkotlin%2Fio%2Fgithub%2Fcomposefluent%2Fcomponent%2FLiteFilter.kt#L133-L164|https://github.com/compose-fluent/compose-fluent-ui/blob/dev/fluent%2Fsrc%2FcommonMain%2Fkotlin%2Fio%2Fgithub%2Fcomposefluent%2Fcomponent%2FLiteFilter.kt#L133-L164>