-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: refacto dropdowns #697
Conversation
✅ Deploy Preview for testitori ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for teritori-dapp ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
However i just fix the behavior of the component, but not the refacto of it. |
4773358
to
55d8221
Compare
2abf1ab
to
ae633a1
Compare
ae633a1
to
43128a0
Compare
const dropdownRef = useRef<View>(null); | ||
|
||
return ( | ||
<View style={{ position: "relative" }}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems that by default all the View has position relative
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
43128a0
to
6611cff
Compare
Signed-off-by: clegirar <[email protected]>
Signed-off-by: clegirar <[email protected]>
6611cff
to
99a5b55
Compare
This
tree dots
components were not consistant, especially when we clicked outside of the dropdown, all dropdowns had not same behaviorSo i gave it back consistant, for the first one (first screen) was good and works well !
For the second one (second screen), you probably just forgot to put the ref in the parent view of the dropdown
For the last one (last image), it was just not implemented :)
Signed-off-by: clegirar [email protected]