Tom Corvus

Hi @Elena12345, You can fix this issue by removing the `overflow: hidden;` on A elements. See below: ``` .flexnav li a { position: relative; display: block; padding: .96em; z-index: 2;...

@becca-bailey is it something that can be implanted in Victory?

@ryan-roemer Do you think it can be fixed? Thanks 🙏

I had the same issue and I use Bootstrap. You can find my code below: ``` html // JQUERY STICKY KIT // http://leafo.net/sticky-kit/ $("#pinned").stick_in_parent({ parent: '.main-wrapper', offset_top: 30 }); ```...

@ken0nek I patch the file but I still have the warning. Did you try your fix with section list reference? `const sectionList = useRef(null);`

Hi @jagwingchoy, I had the same problem with the `` component. I resolved this on putting `` in `` `FooterComponent` prop like this: ``` Hi There! ```

Hi, Do you try to update `react-native-modalize` to 2.0.8 version? There are some fixes about position and OS compatibilities since 2.0.0.

hi @asalha, You can try to put the `SafeAreaView` in Modalize `FooterComponent` prop. https://github.com/jeremybarbet/react-native-modalize/issues/286#issuecomment-782104919 or try the @jagwingchoy solution with `react-native-safe-area-context` `useSafeAreaInsets` hook. https://github.com/th3rdwave/react-native-safe-area-context#usesafeareainsets

Hi @devinnow8, please read this comment. Maybe It can help you to resolve your issue : https://github.com/jeremybarbet/react-native-modalize/issues/335#issuecomment-858744991

Hi @acharyakavita , do you have a roadmap to know when components will be available on this new version?