[$250] mWeb/Chrome - Account Management page - Required section name is not visible

[kbecciv]

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

---

Issue found when executing PR #12147

Action Performed:

1. Go to https://help.expensify.com/articles/other/Account-Management#how-do-i-contact-my-account-manager

Expected Result:

"How do I contact my account manager?" section of "Account Management" page should be displayed with section name visible.

Actual Result:

"How do I contact my account manager?" section name is not visible once user is landed on the page. Only Android / Chrome. Not repro with iOS / Safari nor Windows / Chrome

Workaround:

Unknown

Platform:

Where is this issue occurring?

• Mobile Web - Android/Chrome

Version Number: 1.2.19.1

Reproducible in staging?: Yes

Reproducible in production?: Yes

Email or phone of affected tester (no customers):

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

Notes/Photos/Videos: Any additional supporting documentation

Bug5795351_video_2022-10-27_13-29-37.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[melvin-bot]

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

[sophiepintoraetz]

Hmm, I'm not sure if this needs to go to engineering or if we can close as a part of the Deploy list above - but swinging over in case.

[melvin-bot]

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

[sophiepintoraetz]

Actually, cc @marcochavezf and @johncschuster from https://github.com/Expensify/Expensify/issues/188579

[michaelhaxhiu]

Switching back to daily per the standard bugzero process. Also just a friendly reminder to keep the pressure on to find a contributor and get this one closed out!

A few questions to help move this forward.

1. Is this external or internal?
2. If it's external let's post it to upwork. If it's internal and reproducible, let's label as demolition to get movement.

[sophiepintoraetz]

I'd love to hear from @marcochavezf and @johncschuster to confirm that it's a quick fix from https://github.com/Expensify/Expensify/issues/188579

[marcochavezf]

Oh I missed the previous ping, I think it can be external. Contributors can follow these instructions to run the site locally. I tried to update some of the tocbot settings, but I have no luck. Probably it's a CSS style issue.

[sophiepintoraetz]

Bumping @roryabraham 🙏

[roryabraham]

Sorry for the delay, marking this as external

[melvin-bot]

Current assignee @sophiepintoraetz is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

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

[melvin-bot]

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

[sophiepintoraetz]

Job posted!

[kzhein]

Proposal

Expensify help website has a fixed navigation menu for small screens that usually remains fixed at the top of the page. When you use the URL anchor, the browser window will scroll itself (instantly) to bring anchor at the top of the page, leaving the content behind the fixed navigation menu.

Solution:

expensify.mp4

For small screens, we can use :before pseudo element and giving it a height, which pushes up the size of the header, then use negative margin to yank it back up into place

#content-area {
  h1::before, h2::before {
    @include maxBreakpoint($breakpoint-tablet) {
            display: block;
            content: ' ';
            height: 80px; 
            margin-top: -80px;
            visibility: hidden;
    }
  }
}

[melvin-bot]

Looks like something related to react-navigation may have been mentioned in this issue discussion.

As a reminder, please make sure that all proposals are not workarounds and that any and all attempt to fix the issue holistically have been made before proceeding with a solution. Proposals to change our DeprecatedCustomActions.js files should not be accepted.

Feel free to drop a note in #expensify-open-source with any questions.

[sobitneupane]

Workaround proposed by @kzhein looks good and test well.

As I am not very much familiar with "help.expensify.com", I am not sure if there is any other direct ways to achieve the result.

cc: @Julesssss

🎀👀🎀 C+ reviewed

[melvin-bot]

📣 @kzhein You have been assigned to this job by @Julesssss!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

[kzhein]

Thanks! I have sent a pull request and applied the job in Upwork.

[sophiepintoraetz]

@Julesssss - are we waiting on a review from @Gonals in the linked PR for this issue to close it out?

[Gonals]

@Julesssss - are we waiting on a review from @Gonals in the linked PR for this issue to close it out?

Nope! That PR is already merged and deployed. This issue should be closed, right @Julesssss ?

[Julesssss]

Ah, the automated message didn't appear but we are still 2 days away from payment. Then we can close the issue.

[mvtglobally]

Issue not reproducible during KI retests. (First week)

[kzhein]

@sophiepintoraetz May I know when can I expect the payment?

[sophiepintoraetz]

Hey @kzhein - typically we need 7 days from the PR being merged but you're all set! Just processed payment through Upwork now 👍 @sobitneupane - I've hired you for the job if you want to accept the contract!

[sobitneupane]

@sophiepintoraetz Accepted offer. This issue is also eligible for 50% bonus since the PR was merged within 3 days.

[roryabraham]

Dropping this since @Julesssss has been acting as the CME for this issue.

[kzhein]

@sophiepintoraetz Received the payment but I think you forgot the eligible 50% bonus.

[sophiepintoraetz]

Sorry @kzhein - I was out yesterday - I'll look into this once I have a chance!

[mvtglobally]

Issue not reproducible during KI retests. (Second week)

[sophiepintoraetz]

@kzhein - thanks for your patience! I created a separate job I hired you for with the bonus of $125 - see here!

[sophiepintoraetz]

All paid!

[sobitneupane]

@sophiepintoraetz Accepted offer. This issue is also eligible for 50% bonus since the PR was merged within 3 days.

@sophiepintoraetz I am not paid yet. I have accepted the offer.

[sophiepintoraetz]

Hired you for the job @sobitneupane - here's the link!

[sobitneupane]

@sophiepintoraetz Thanks. (250$+125$) is due.

[sophiepintoraetz]

All set @sobitneupane