Skip to content
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

[$500] Dev: Web - Inconsistence space between input fields in #Rooms #27604

Closed
1 of 6 tasks
kbecciv opened this issue Sep 16, 2023 · 21 comments
Closed
1 of 6 tasks

[$500] Dev: Web - Inconsistence space between input fields in #Rooms #27604

kbecciv opened this issue Sep 16, 2023 · 21 comments
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors

Comments

@kbecciv
Copy link

kbecciv commented Sep 16, 2023

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!


Action Performed:

  1. Click on FAB icon and select Send message option
  2. Go to #Room tab
  3. Check space between input fields

Expected Result:

Space should be consistence between input fields

Actual Result:

Space under Room name is more compare to other

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android / native
  • Android / Chrome
  • iOS / native
  • iOS / Safari
  • MacOS / Chrome / Safari
  • MacOS / Desktop

Version Number: Dev 1.3.70.5
Reproducible in staging?: n
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Screen.Recording.2023-09-16.at.10.37.38.AM.mov

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694840876055859

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01df923e800f40dae5
  • Upwork Job ID: 1703144278120108032
  • Last Price Increase: 2023-09-23
@kbecciv kbecciv added External Added to denote the issue can be worked on by a contributor Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. labels Sep 16, 2023
@c3024
Copy link
Contributor

c3024 commented Sep 16, 2023

Proposal

Please re-state the problem that we are trying to solve in this issue.

Margin below room name is more than the bottom margin for other fields below

What is the root cause of that problem?

We are using a different margin here

<View style={styles.mb5}>

which is different here
<View style={styles.mb2}>

What changes do you think we should make in order to solve the problem?

We should use the same margin mb2 for all including room name input view.

What alternative solutions did you explore? (Optional)

@melvin-bot melvin-bot bot changed the title Dev: Web - Inconsistence space between input fields in #Rooms [$500] Dev: Web - Inconsistence space between input fields in #Rooms Sep 16, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 16, 2023

Triggered auto assignment to @puneetlath (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

@melvin-bot
Copy link

melvin-bot bot commented Sep 16, 2023

Job added to Upwork: https://www.upwork.com/jobs/~01df923e800f40dae5

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Sep 16, 2023
@melvin-bot
Copy link

melvin-bot bot commented Sep 16, 2023

Bug0 Triage Checklist (Main S/O)

  • This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
  • This bug is not a duplicate report (check E/App issues and #expensify-bugs)
    • If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
  • This bug is reproducible using the reproduction steps in the OP. S/O
    • If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
    • If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
  • This issue is filled out as thoroughly and clearly as possible
    • Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
  • I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@melvin-bot
Copy link

melvin-bot bot commented Sep 16, 2023

Triggered auto assignment to @laurenreidexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@melvin-bot
Copy link

melvin-bot bot commented Sep 16, 2023

Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee (External)

@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Sep 16, 2023

Proposal

Please re-state the problem that we are trying to solve in this issue

Inputs have different distances between them

What is the root cause of that problem?

Different styles in inputs

What changes do you think we should make in order to solve the problem?

In this component we have the some inputs which have some different styles

<View style={styles.mb5}>
<RoomNameInput
inputID="roomName"
isFocused={props.isFocused}
shouldDelayFocus
autoFocus
/>
</View>
<View style={styles.mb2}>
<Picker
inputID="policyID"
label={translate('workspace.common.workspace')}
placeholder={{value: '', label: translate('newRoomPage.selectAWorkspace')}}
items={workspaceOptions}
onValueChange={setPolicyID}
/>
</View>
{isPolicyAdmin && (
<View style={styles.mb2}>
<Picker
inputID="writeCapability"
label={translate('writeCapabilityPage.label')}
items={writeCapabilityOptions}
defaultValue={CONST.REPORT.WRITE_CAPABILITIES.ALL}
/>
</View>
)}
<View style={styles.mb2}>
<Picker
inputID="visibility"
label={translate('newRoomPage.visibility')}
items={visibilityOptions}
onValueChange={setVisibility}
defaultValue={CONST.REPORT.VISIBILITY.RESTRICTED}
/>
</View>

To reduce potential errors, it would be a good idea to create a constant for styles so that you can change styles in only one place

Or create a wrapper component for the inputs

What alternative solutions did you explore? (Optional)

NA

@laurenreidexpensify
Copy link
Contributor

@jjcoffee what you reckon about the proposal above?

@c3024
Copy link
Contributor

c3024 commented Sep 18, 2023

Here is a proposal as well just in case it is missed @jjcoffee

@jjcoffee
Copy link
Contributor

@c3024's proposal looks good - correct RCA and solution. I'm not 100% sure if this wasn't intentional, so we might want some design eyes to verify that we want to get rid of the spacing here.

@shawnborton or @dannymcclain Are we good to reduce the margin below the "Room name" input to match the other inputs?
image

🎀👀🎀 C+ reviewed

@melvin-bot
Copy link

melvin-bot bot commented Sep 20, 2023

Triggered auto assignment to @tylerkaraszewski, see https://stackoverflow.com/c/expensify/questions/7972 for more details.

@dannymcclain
Copy link
Contributor

Looking at some other mocks with multiple inputs, I actually think the spacing between the Room name and Workspace inputs are what we want them all to have. Here's a random example:
image

@shawnborton can verify but I'm pretty sure we want to add space here, not remove it.

@jjcoffee
Copy link
Contributor

@dannymcclain Ah so you're saying we should increase the spacing on all the other inputs instead?

@dannymcclain
Copy link
Contributor

I believe so!

@c3024
Copy link
Contributor

c3024 commented Sep 20, 2023

We use this between inputs

View style={styles.formSpaceVertical}

in address page so is this what we use here as well?

Edit: This is a different address page and different pages have different spacing. So we might use mb5 here for all then.

@shawnborton
Copy link
Contributor

Yup, that makes sense to me. Though I think @dangrous is working on revamping this page right now so maybe we want to just close this issue out in favor of the work DGR is doing?

@dangrous
Copy link
Contributor

Yep I can tackle that in my PR. Do you mind commenting with what it should be (looks like mb5 I think?) on this PR?

@shawnborton
Copy link
Contributor

Can do. Okay, @laurenreidexpensify let's close this one down.

@melvin-bot
Copy link

melvin-bot bot commented Sep 23, 2023

📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸

@melvin-bot melvin-bot bot added the Overdue label Sep 23, 2023
@gadhiyamanan
Copy link
Contributor

@laurenreidexpensify i think this is eligible for reporting bonus because it will be handled in other PR after i reported this issue

@gadhiyamanan
Copy link
Contributor

Bump @laurenreidexpensify

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 External Added to denote the issue can be worked on by a contributor Help Wanted Apply this label when an issue is open to proposals by contributors
Projects
None yet
Development

No branches or pull requests