-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[$250] iOS - Distance - Center icon overlaps with compass icon #44486
Comments
Triggered auto assignment to @trjExpensify ( |
@trjExpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #vip-vsp |
ProposalPlease re-state the problem that we are trying to solve in this issue.iOS - Distance - Center icon overlaps with compass icon What is the root cause of that problem?The centre icon is placed with App/src/components/MapView/MapView.tsx Lines 269 to 281 in 67186f1
What changes do you think we should make in order to solve the problem?Adjust the padding to change the position of the icon to bottom left/right. What alternative solutions did you explore? (Optional)Options 1. Hide the compass using Options 2. Updated compass position using Option 3. Compass can also be hidden by positioning it just below the center button |
Hm, @Expensify/design I'm not sure on this. Do we literally just cover the compass icon in the background or should it not be there at all? |
Ah interesting, that only shows up if you rotate the map I bet? |
Yup you're right. I had never seen that compass before but I just tested out rotating the map and that's when it shows up. Womp. |
Goooot it. So both of these UI elements need to live together in the same view then conceivably? |
It looks like we can also just move the compass or disable it entirely. From here: So I like the idea of maybe moving the compass to the bottom right or something? Curious what @Expensify/design thinks. |
Got it. Bottom right, above the info button? We can pay a retainer to get rid of all the Mapbox stuff at the bottom at some point in the future. I think we should keep the compass, as I think it's pretty standard when turning the map to reorientate it. |
Yeah, that's what I was thinking. And the info button would typically always show because the default view is not to rotate the map. |
Sounds good! |
@shawnborton @trjExpensify, what do you think about placing the compass below the scale bar? I think it relates to the scale bar and should be positioned near it. below_scalebar.mp4 |
Works for me, but I'll defer to Shawn! |
I like it beneath the scale bar—it does feel kinda related and tucks up in there nicely. Will also wait for Shawn to weigh in 🙂 |
Oh I really like that too, let's do it |
@trjExpensify, can we apply the external label to get this moving? |
Let's do it! |
Job added to Upwork: https://www.upwork.com/jobs/~01c7fdbfc969413a5e |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ahmedGaber93 ( |
@Krishna2323's alternative solutions option 2 using 🎀 👀 🎀 C+ reviewed |
Triggered auto assignment to @lakchote, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.2-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
Center icon will not overlap with compass icon
Actual Result:
Center icon overlaps with compass icon
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6525406_1719418260738.RPReplay_Final1719412840.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @ahmedGaber93The text was updated successfully, but these errors were encountered: