Skip to content

Commit 729c53c

Browse files
authored
Update FAQ.md
1 parent 711365a commit 729c53c

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

FAQ.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,12 +5,12 @@ The reveal effect is not exactly above the element to be revealed.
55
![Misplaced](./assets/faq_misplaced.png)
66

77
This should not occur for apps written completely in Compose and is likely an interoperability issue
8-
between legacy Android views and Compose. It might occur when you place a `ComposeView` in a View
8+
between legacy Android views and Compose. It might happen when you place a `ComposeView` in a View
99
layout with other views placed above or around. Reveal
1010
uses [positionInRoot](https://developer.android.com/reference/kotlin/androidx/compose/ui/layout/LayoutCoordinates#(androidx.compose.ui.layout.LayoutCoordinates).positionInRoot())
11-
to determine the position of revealable items. "Root" in this case is the root composable. If the
12-
root composable is also the root view like in full-compose apps, this is not a problem. However
13-
if the `ComposeView` is somewhere else in the view hierarchy, that might cause this problem. To
14-
work around it, specify the additional offset to be applied to all revealables with the
11+
to determine the position of revealable items. "Root" in this case is the root composable. This issue
12+
does not happen if the root composable is also the root view like in full-compose apps. However
13+
placing the `ComposeView` somewhere else in the view hierarchy might cause this problem.
14+
To work around it, specify the additional offset to be applied to all revealables with the
1515
`revealableOffset` parameter of the `FullscreenRevealOverlayInserter` which is passed to the
1616
`overlayInserter` argument of the `RevealCanvas` composable.

0 commit comments

Comments
 (0)