handle focus after edit report item by suneox · Pull Request #42965 · Expensify/App

suneox · 2024-06-02T09:48:04Z

Details

Fixed Issues

$ #40767
PROPOSAL: #40767 (comment)

Tests

Go to any chat.
Send a message with 10 line breaks.
Tap and hold on the recently sent message.
Tap on "Edit comment".

Verify that the page auto-scrolls to the bottom and the compose box is fully visible without manual scroll.

Verify that no errors appear in the JS console

Offline tests

QA Steps

Go to any chat.
Send a message with 10 line breaks.
Tap and hold on the recently sent message.
Tap on "Edit comment".

Verify that the page auto-scrolls to the bottom and the compose box is fully visible without manual scroll.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Screen.Recording.2024-06-02.at.16.04.21.mov

Android: mWeb Chrome

Screen.Recording.2024-06-02.at.16.02.34.mov

iOS: Native

Screen.Recording.2024-06-02.at.15.26.54.mov

iOS: mWeb Safari

Screen.Recording.2024-06-02.at.15.51.31.mov

MacOS: Chrome / Safari

Screen.Recording.2024-06-02.at.15.58.14.mov

MacOS: Desktop

Screen.Recording.2024-06-02.at.16.05.52.mov

melvin-bot · 2024-06-02T09:48:09Z

@rojiphil Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

suneox · 2024-06-02T09:50:00Z

Hi @rojiphil, The PR is ready to review

rojiphil · 2024-06-03T11:43:35Z

src/pages/home/report/ReportActionItemMessageEdit.tsx

+                                        reportScrollManager.scrollToIndex(index, true);
+                                    });
+                                });
                                reportScrollManager.scrollToIndex(index, true);


Is there a need to call scrollToIndex here again even after calling within requestAnimationFrame?

Ah we don't need to call this function, I'll remove now thank you

@rojiphil I have updated and re-test

Screen.Recording.2024-06-03.at.20.54.13.mov

rojiphil · 2024-06-03T16:53:28Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

MacOS: Chrome / Safari

42965-web-safari-001.mp4

Android: Native

42965-android-native-001.mp4

Android: mWeb Chrome

42965-mweb-chrome-001.mp4

iOS: Native

42965-ios-native-001.mp4

iOS: mWeb Safari

42965-mweb-safari-001.mp4

MacOS: Desktop

42965-desktop-001.mp4

rojiphil

@suneox Just one small request for change. In the tests section, please change the wording of the expected behavior to the following as that would help QA:
Verify that the page auto-scrolls to the bottom and the compose box is fully visible without manual scroll.

Otherwise, code LGTM. Tests well and completed checklist too.

suneox · 2024-06-04T00:54:26Z

@suneox Just one small request for change. In the tests section, please change the wording of the expected behavior to the following as that would help QA: Verify that the page auto-scrolls to the bottom and the compose box is fully visible without manual scroll.

Otherwise, code LGTM. Tests well and completed checklist too.

Thank you, I have updated

suneox · 2024-06-06T12:32:47Z

Hi @thienlnam have you got any feedback on this PR?

OSBotify · 2024-06-06T14:45:36Z

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

OSBotify · 2024-06-11T23:33:49Z

🚀 Deployed to production by https://github.com/luacmartins in version: 1.4.81-11 🚀

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

…dit-last-message" This reverts commit 478db52, reversing changes made to bb14c99.

…edit-last-message" This reverts commit 747fe19.

handle focus after edit report item

3496879

suneox requested a review from a team as a code owner June 2, 2024 09:48

melvin-bot bot requested review from rojiphil and removed request for a team June 2, 2024 09:48

rojiphil reviewed Jun 3, 2024

View reviewed changes

remove redundant code

2c2e598

rojiphil approved these changes Jun 3, 2024

View reviewed changes

melvin-bot bot requested a review from thienlnam June 3, 2024 17:01

thienlnam approved these changes Jun 6, 2024

View reviewed changes

thienlnam merged commit 478db52 into Expensify:main Jun 6, 2024

github-actions bot mentioned this pull request Jun 10, 2024

Deploy Checklist: New Expensify 2024-06-10 #43344

Closed

melvin-bot bot mentioned this pull request Jun 11, 2024

[HOLD for payment 2024-07-10] [HOLD for payment 2024-06-20] [HOLD for payment 2024-06-18] [$250] Chat - Compose box is hidden when editing multiple line break message #40767

Closed

6 tasks

mananjadhav added a commit to mananjadhav/App that referenced this pull request Jun 19, 2024

Revert "Merge pull request Expensify#42965 from suneox/40767-handle-e…

747fe19

…dit-last-message" This reverts commit 478db52, reversing changes made to bb14c99.

mananjadhav added a commit to mananjadhav/App that referenced this pull request Jun 19, 2024

Reapply "Merge pull request Expensify#42965 from suneox/40767-handle-…

8c0912a

…edit-last-message" This reverts commit 747fe19.

suneox deleted the 40767-handle-edit-last-message branch May 25, 2025 09:33

blazejkustra mentioned this pull request Feb 20, 2026

[BATCH 8] Input Focus usages #83069

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

handle focus after edit report item#42965

handle focus after edit report item#42965
thienlnam merged 2 commits intoExpensify:mainfrom
suneox:40767-handle-edit-last-message

suneox commented Jun 2, 2024 •

edited

Loading

Uh oh!

melvin-bot bot commented Jun 2, 2024

Uh oh!

suneox commented Jun 2, 2024

Uh oh!

rojiphil Jun 3, 2024

Uh oh!

suneox Jun 3, 2024

Uh oh!

suneox Jun 3, 2024

Uh oh!

rojiphil commented Jun 3, 2024

Uh oh!

rojiphil left a comment

Uh oh!

suneox commented Jun 4, 2024

Uh oh!

suneox commented Jun 6, 2024

Uh oh!

OSBotify commented Jun 6, 2024

Uh oh!

OSBotify commented Jun 11, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

suneox commented Jun 2, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Jun 2, 2024

Uh oh!

suneox commented Jun 2, 2024

Uh oh!

rojiphil Jun 3, 2024

Choose a reason for hiding this comment

Uh oh!

suneox Jun 3, 2024

Choose a reason for hiding this comment

Uh oh!

suneox Jun 3, 2024

Choose a reason for hiding this comment

Uh oh!

rojiphil commented Jun 3, 2024

Reviewer Checklist

Screenshots/Videos

Uh oh!

rojiphil left a comment

Choose a reason for hiding this comment

Uh oh!

suneox commented Jun 4, 2024

Uh oh!

suneox commented Jun 6, 2024

Uh oh!

OSBotify commented Jun 6, 2024

Uh oh!

OSBotify commented Jun 11, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

suneox commented Jun 2, 2024 •

edited

Loading