Adam Gerthel

@Dragomir-Ivanov Right, but just because use exploit that fact that it functions like this doesn't mean that it's expected behaviour. I personally would expect an "update" hook to run on...

> Just a thought but is there a chance the form is rendered before the initial values are available and adding them to an existing form could be the culprit?...

+1

@janicduplessis The iPhone is running 13.1.2. react-native-safe-area-context is on `~0.3.6` (installed via `expo install react-native-safe-area-context` since I'm using Expo).

@janicduplessis I'm not sure I follow, the issue is reproducible in your snack (using react-native-safe-area-context 0.6.0), but you're saying the issue has already been fixed? Are you saying that this...

Oh, I see, I was a little confused since the package.json in your Snack example lists version 0.6.0. Anyway, I'll just wait for the next Expo release then. Thanks!

I've upgraded Expo and I'm using `0.6.0` but the issue persists. Your snack has the same issue still.

It's been a while since I work of those parts of the code but... seems like it, yes.

Agree - I've contemplated adding similar components. I rarely have need for all insets on a single view.

I've just started looking for popover solutions that support both DOM and Native and haven't found any. This is the most popular repository with DOM support (Along with react-popper), and...