there is no camera on screenshots, in most cases camera cut the UI elements in the toolbar




Padding for address bar in Browser needs to be the same when url is opened as when no url is opened (10px).
@errorists believe this fix is required regardless of changes to RN, as it's an inconsistency of the address bar padding between Main browser screen and opened url browser screen.
cc @rachelhamlin
@hesterbruikman ur right, needs a fix
Thanks for the images @hesterbruikman. I'll put an xs bounty on it. If we maintain the same padding across main screen and opened browser window that will solve it?
Our top toolbar should start at the position of the cutout, to make it right we'd need to ask the magic number where the cutout ends to position the UI correctly. I'd assume it's possible to fetch this position from RN. There is the safeAreaView we already use for new iPhones where we position the toolbar at 44px from the top, same needs to happen for S10.
Adding to this; Chat view shows the same issue although it's less severe as there is no component obtruded by the camera. Still needs the safeAreaView equivalent.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
__This issue now has a funding of 40.0 DAI (40.0 USD @ $1.0/DAI) attached to it.__
@hackereunji Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
@hackereunji Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
This issue might in some ways relate to statusBar which is also a concern of #8981 [Topbar] 🤔 . And what is done to resolve this, could affect that general area.
Keeping an eye on this one :)
@hackereunji Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
@hackereunji Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Hey there @hackereunji any progress here? Shall I take you off it?
Oh, sorry for the inconvenience! I was thinking about how to fix it.... but please take me off it! This is so hard for me:( Good luck for your work!
Okay, thanks for your reply @HackerEunji :) All the best.
@hackereunji Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
@hackereunji due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!
Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days
we could consider this library https://github.com/th3rdwave/react-native-safe-area-context
fixed
Issue Status: 1. Open 2. Cancelled
__The funding of 40.0 SAI (40.0 USD @ $1.0/SAI) attached to this issue has been cancelled by the bounty submitter__