Skip to content

[Hold for Payment] Manage cards button is not visible when viewport is ~840px #4659

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

Closed
isagoico opened this issue Aug 13, 2021 · 25 comments · Fixed by #4793
Closed

[Hold for Payment] Manage cards button is not visible when viewport is ~840px #4659

isagoico opened this issue Aug 13, 2021 · 25 comments · Fixed by #4793
Assignees
Labels
Engineering External Added to denote the issue can be worked on by a contributor Weekly KSv2

Comments

@isagoico
Copy link

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. Navigate to a workspace
  2. Reduce to viewport to be ~840px

Expected Result:

Button should be completely visible.

Actual Result:

Button is cropped and not completely visible.

Workaround:

No need, visual issue.

Platform:

Where is this issue occurring?

  • Web
  • mWeb (tablets or iPads maybe?)

Version Number: 1.0.85-0

Logs: https://stackoverflow.com/c/expensify/questions/4856

Notes/Photos/Videos: Any additional supporting documentation

image

Expensify/Expensify Issue URL:

View all open jobs on Upwork


From @vitHoracek https://expensify.slack.com/archives/C01GTK53T8Q/p1628855161330000

With the added inset for the workspace modal it seems we will need to update the styles for Manage cards box, the text and button gets out of the blue container when the viewport is ~840px. This is on current main .

@MelvinBot
Copy link

Triggered auto assignment to @francoisl (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

@kakajann
Copy link
Contributor

kakajann commented Aug 14, 2021

Proposal

840px is actually a tablet size. I tried to fix the issue, but it's kind of impossible with the current structure.

So, the best way to fix this is to create a condition to detect tablet sizes.

  1. create a new variable in src/styles/variables.js.
tabletResponsiveWidthBreakpoint: 1024
  1. modify src/components/withWindowDimensions.js
const isMediumScreenWidth = initialDimensions.width >= variables.mobileResponsiveWidthBreakpoint
    && initialDimensions.width <= variables.tabletResponsiveWidthBreakpoint;
  1. Finally pass this style isMediumScreenWidth && styles.w100 to the card content
    <View
    style={[
    styles.flexGrow1,
    styles.justifyContentEnd,
    styles.alignItemsStart,
    !isSmallScreenWidth && styles.w50,
    ]}
    >

@kakajann
Copy link
Contributor

Result

Screen Shot 2021-08-14 at 6 48 53 AM

@mananjadhav
Copy link
Collaborator

@kakajann I had similar findings and we were tracking this issue here #4421

The current structure doesn't factor in any Tablet device dimensions.

@francoisl francoisl added the External Added to denote the issue can be worked on by a contributor label Aug 14, 2021
@francoisl francoisl removed their assignment Aug 14, 2021
@MelvinBot
Copy link

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

@SofiedeVreese
Copy link
Contributor

@shawnborton would love your thoughts here, given the similarities to #4421 and you mentioned we don't plan on changing the breakpoint?

@kakajann
Copy link
Contributor

No need to change the breakpoints in my opinion. Just add new breakpoint to make some components responsive for tablet sizes. (i.e between 800 and 1024 pixels)

It will help us to fix current issue and for future use.

@mananjadhav
Copy link
Collaborator

I agree with @kakajann. We should be adding a new breakpoint for tablet sizes and probably rethink on certain pages.

@shawnborton
Copy link
Contributor

I think that makes sense to me, curious if anyone else from @Expensify/design agrees. To summarize, we basically have a weird set of screen widths between like 800px-1000px wide where this Expensify Card advertorial breaks down. It sounds like the actual design of the advertorial for mobile devices would look better in these cases.

@megankelso
Copy link

sorry for the confusion, but is this the proposal? essentially having the cards layered behind the text?

I know these are different sizes, but I noticed the cards are changing size and position. Curious if there's a way to keep them more consistent with the screen below?
129406961-6f7898e7-19ed-487c-850f-dad8f3e460e8

@SofiedeVreese
Copy link
Contributor

SofiedeVreese commented Aug 16, 2021

@megankelso if from a Design point of view you agree this is something we want to fix, then I'll push it to Upwork and we can gather more proposals and see if there are other ways to fix the issue!

I just wanted to make sure we all agree this is an issue before pushing it to Upwork.

@megankelso
Copy link

oh I'm sorry for the misunderstanding. yes, I think it is worth fixing!

@SofiedeVreese
Copy link
Contributor

@megankelso no stress- it was a little vague in the thread so sorry for causing confusion!

Ok pushing to Upwork! https://www.upwork.com/jobs/~0104471d011b7f47f4

@kakajann please see @megankelso 's comment above, is there a way to keep things more consistent with the screenshot in her comment?

@MelvinBot MelvinBot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Aug 17, 2021
@MelvinBot
Copy link

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

@mamdouhsobhy
Copy link

must resize views and user constrain to update the place of button

@kakajann
Copy link
Contributor

@SofiedeVreese, @megankelso Yes, I can keep it consistent, once I add a new viewport for tablets.

@Christinadobrzyn Christinadobrzyn added Help Wanted Apply this label when an issue is open to proposals by contributors and removed Help Wanted Apply this label when an issue is open to proposals by contributors labels Aug 17, 2021
@SofiedeVreese
Copy link
Contributor

@timszot would love your 2c on the above, thanks!

@MelvinBot MelvinBot removed the Overdue label Aug 20, 2021
@timszot
Copy link
Contributor

timszot commented Aug 20, 2021

@kakajann I like that proposal and seems like design likes it too!

@SofiedeVreese let's get them hired!

@SofiedeVreese
Copy link
Contributor

Hey @kakajann Can you submit your proposal via Upwork so I can hire you through Upwork? Thanks!

@kakajann
Copy link
Contributor

Hi, just submitted

@kakajann
Copy link
Contributor

Can anybody assign me? It make it easier to sort the issues that I'm working on

@SofiedeVreese
Copy link
Contributor

Hired & will assign you now @kakajann

@MelvinBot MelvinBot removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Aug 21, 2021
@MelvinBot MelvinBot removed the Overdue label Aug 24, 2021
@timszot timszot reopened this Aug 24, 2021
@timszot
Copy link
Contributor

timszot commented Aug 24, 2021

@SofiedeVreese This is merged, but not deployed yet.

@timszot timszot added Weekly KSv2 and removed Daily KSv2 labels Aug 25, 2021
@SofiedeVreese
Copy link
Contributor

SofiedeVreese commented Aug 30, 2021

Looking at this comment, looks like it's deployed now! Holding for payment on 6 September.

Edit: time zones confuse me, should be September 8th per this comment.

@SofiedeVreese SofiedeVreese changed the title Manage cards button is not visible when viewport is ~840px [Hold for Payment] Manage cards button is not visible when viewport is ~840px Aug 30, 2021
@SofiedeVreese
Copy link
Contributor

This is paid out now @kakajann ! Thanks for your work on this!

Contributor paid, the contract has been completed, and the Upwork post has been closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Engineering External Added to denote the issue can be worked on by a contributor Weekly KSv2
Projects
None yet
Development

Successfully merging a pull request may close this issue.