Skip to content

fix: input styles #5742

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

Merged
merged 1 commit into from
Oct 11, 2021
Merged

fix: input styles #5742

merged 1 commit into from
Oct 11, 2021

Conversation

parasharrajat
Copy link
Member

@parasharrajat parasharrajat commented Oct 9, 2021

Details

#5462 (comment)

Fixed Issues

$ #5462

Tests | QA Steps

Open NewDot on all the below-listed platforms one by one and follow the following procedure.

  1. Open Profile Page.
  2. Check the Input for FirstName and LastName is proper as per the issue description.
  3. Check the Pronoun Dropdown is proper.

Tested On

  • Web
  • Mobile Web
  • Desktop
  • iOS
  • Android

Screenshots

Web | Desktop

image

Mobile Web

iOS

Android

Screenshot 2021-10-09 20:23:03

@parasharrajat parasharrajat requested a review from a team as a code owner October 9, 2021 13:35
@MelvinBot MelvinBot requested review from pecanoro and removed request for a team October 9, 2021 13:35
@pecanoro pecanoro merged commit e484a75 into Expensify:main Oct 11, 2021
@OSBotify
Copy link
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@parasharrajat
Copy link
Member Author

@pecanoro Sadly this was supposed to be on n6-hold. But it's not a big one so I will take care of any issues if caused by this.

@shawnborton Please have a look and let me know what do you think about the changes?

It's merged but I have an open follow-up if you have some changes.

@shawnborton
Copy link
Contributor

Based on this screenshot here:
image

It looks like there is a difference in the location of the form label depending on whether or not we use a text input or a selector. These should literally be exactly the same location - the only difference is that one of them has a dropdown arrow and the other doesn't.

@parasharrajat
Copy link
Member Author

parasharrajat commented Oct 11, 2021

Yeah, It looks like it. Let me check

@parasharrajat
Copy link
Member Author

parasharrajat commented Oct 11, 2021

@shawnborton How about this?
image

@shawnborton
Copy link
Contributor

I think that looks good, but to make sure, can you update the text input and the select menu to have the same exact labels and values? This will make it very easy to compare (by putting them on top of each other)

@parasharrajat
Copy link
Member Author

@shawnborton Does this work?
image

@shawnborton
Copy link
Contributor

Great! So it looks like the value is in the same place on both, but the label is off by 1px. On the select menu, the label is 1px lower than on the select menu.

But that being said, I think the value actually needs to go up by 1px as well.

So to recap:

  • label position of the text input above
  • value position goes up by 1px on both

@parasharrajat
Copy link
Member Author

What did you say?

  1. Position the label towards up by 1px in input.
  2. and move the value in both up by 1px.

@shawnborton
Copy link
Contributor

Ah let me rephrase:

  1. Move the label of the select menu up by 1px. The label on the text input is good.
  2. Move the value in both up by 1px

@marcaaron
Copy link
Contributor

I think this maybe caused a regression to our error styles 😢

All of these fields are now missing outlines.

2021-10-12_13-31-04

@aldo-expensify
Copy link
Contributor

aldo-expensify commented Oct 13, 2021

The missing outline for ExpensiPicker seems to be related to this change:

https://github.com/Expensify/App/pull/5742/files#diff-8ab8ba45ab927f1430b8d1209d187e003a9cdfe476f809e4483ef64cdba253ebL542-R551

I may be wrong, but it looks like the border was moved from the picker's outer container to the picker itself? so maybe the red border color wasn't moved consistently.

@aldo-expensify
Copy link
Contributor

aldo-expensify commented Oct 13, 2021

It looks like the Company address field lost support for the red outline and error text when it changed to use the new AddressSearch component.

<AddressSearch
label={this.props.translate('common.companyAddress')}
containerStyles={[styles.mt4]}
value={`${this.state.addressStreet} ${this.state.addressCity} ${this.state.addressState} ${this.state.addressZipCode}`}
onChangeText={(fieldName, value) => this.clearErrorAndSetValue(fieldName, value)}

So, this PR only caused the regression for the ExpensiPicker (State and Company Type fields)

@parasharrajat
Copy link
Member Author

This PR was never supposed to merge at this time. But I will submit another asap.

@parasharrajat
Copy link
Member Author

Created a PR to fix the Border issue and other input issues. #5805
cc: @marcaaron @aldo-expensify

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by @pecanoro in version: 1.1.7-25 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

@OSBotify
Copy link
Contributor

🚀 Deployed to production by @roryabraham in version: 1.1.8-9 🚀

platform result
🤖 android 🤖 success ✅
🖥 desktop 🖥 success ✅
🍎 iOS 🍎 success ✅
🕸 web 🕸 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants