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

Try to refactor the logic regarding refocusing when the modal is closed #29199

Closed
wants to merge 47 commits into from

Conversation

ntdiary
Copy link
Contributor

@ntdiary ntdiary commented Oct 10, 2023

So far, the Modal components under our control can be categorized into three types: BaseModal, PopoverWithoutOverlay, and RHP (Right Hand Panel).

This PR will simulate the iOS native Modal refocusing behavior: If there is a focused input field before opening the Modal, our app will attempt to restore that focus after the Modal is dismissed. If there is no focus before opening, no restore after the Modal is dismissed.

Additionally, this PR will introduce a restoreFocusType prop, here are possible values:

  1. default, this will follow the default behavior mentioned above.
  2. preserve, this will leave the focus in the manager and no longer restore focus, applicable for consecutive modal scenarios.
  3. delete, this will delete the focus and no longer restore focus, the caller can decide in its own business logic whether to focus a specific element.

The specific business Modals that have been tested:

  1. context menu (long press / right click a message to open this modal)
  2. three dots menu (click the three dot button in the top right corner of the app to open this modal)
  3. confirm modal (some delete actions will show this modal)
  4. attachment preview modal (click an image message to open this modal)
  5. emoji picker modal (click the emoji button in a composer)
  6. the main composer attachment modal (click the plus button in the main composer to open this modal)
  7. RHP (click the username in a message to open the profile page, or use shortcuts to open some RHP pages)

Once the POC is approved by most people, we'll refine the code, clean things up, and then repush it.

Details

Fixed Issues

$ #29011
$ #24452
PROPOSAL: #24452 (comment)

Tests

context menu modal

case 1 (cancel action)

  1. Open a report.
  2. Focus the main composer.
  3. Send a regular text message.
  4. Long press this message to open the context menu modal (or right click the message for web/desktop platforms).
  5. Click the backdrop or blank area to close the context menu modal.
  6. Verify the main composer will gain focus again.
  7. Make the main composer lose focus.
  8. Repeat step 4 & 5.
  9. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 2 (add reaction + cancel action)

  1. Open a report.
  2. Focus the main composer.
  3. Long press a text message to open the context menu modal.
  4. Click the Add reactionto open the emoji modal.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click the backdrop or blank area to close the emoji modal.
  7. Verify the main composer will gain focus again.
  8. Make the main composer lose focus.
  9. Repeat step 3, 4, 5, and 6.
  10. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 3 (edit coment)

  1. Open a report.
  2. Focus the main composer.
  3. Long press a text message to open the context menu modal.
  4. Select the Edit comment.
  5. Verify the edit composer will gain focus.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 4 (delete comment)

  1. Open a report.
  2. Focus the main composer.
  3. Long press the text message to open the context menu modal.
  4. Select the Delete comment to open the Confirm modal.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click the backdrop / Delete button / Cancel button to close the Confirm modal.
  7. Verify the main composer will gain focus again.
  8. Make the main composer lose focus.
  9. Repeat step 3, 4, 5, and 6.
  10. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop


emoji modal

case 1 (cancel action)

  1. Open any report.
  2. Focus the main composer.
  3. Click the emoji button to open the emoji modal.
  4. Click the backdrop or blank area to close the emoji modal.
  5. Verify the main composer will gain focus again.
  6. Make the main composer lose focus.
  7. Repeat step 3 & 4.
  8. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 2 (cancel action)

  1. Open any report.
  2. Edit a text message.
  3. Click the emoji button in the edit composer to open the emoji modal.
  4. Click the backdrop or blank area to close the emoji modal.
  5. Verify the edit composer will gain focus again.
  6. Make the edit composer lose focus.
  7. Repeat step 3 & 4.
  8. Verify the edit composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 3 (cancel action)

  1. Open any report.
  2. Edit a text message.
  3. Focus the main composer.
  4. Click the emoji button in the edit composer to open the emoji modal.
  5. Click the backdrop or blank area to close the emoji modal.
  6. Verify the main composer will gain focus again.
  • android native
  • android chrome
  • ios native
    main focus didn't show
  • ios web
  • web
  • desktop


Right Hand Panel

case 1 (test by mouse)

  1. Open a report.
  2. Focus the main composer.
  3. Click the top avatar to open the detail page.
  4. Click the backdrop to close the detail page.
  5. Verify the main composer will gain focus again.
  6. Make the main composer lose focus.
  7. Repeat step 3 & 4.
  8. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 2 (test by keyboard shortcuts)

  1. Open a 1:1 report.
  2. Focus the main composer.
  3. Press CMD + J to open the keyboard shortcuts page.
  4. Click the backdrop to close the shortcuts page.
  5. Verify the main composer will gain focus again.
  6. Make the main composer lose focus.
  7. Repeat step 3 & 4.
  8. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop


attachment modal

case 1 (cancel action)

  1. Open a report.
  2. Focus the main composer.
  3. Click the plus button in the main composer to open the first attachment modal.
  4. Click the backdrop or blank area to close the first attachment modal.
  5. Verify the main composer will gain focus again.
  6. Make the main composer lose focus.
  7. Repeat step 3 & 4.
  8. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 2 (first attachment modal + RHP)

  1. Open a report.
  2. Focus the main composer.
  3. Click the plus button to open the first attachment modal.
  4. Select the Request money / Send money / Assign task.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click the top-left back button.
  7. Verify the main composer will gain focus again.
  8. Make the main composer lose focus.
  9. Repeat step 3, 4, 5, and 6.
  10. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
    it seems that the viewport api is not stable.
  • web
  • desktop

case 3 (all mobile platforms: cancel action for the second modal)

  1. Open a report.
  2. Focus the main composer.
  3. Click the plus button to open the first attachment modal.
  4. Select the Add attachment.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click the backdrop to close the second attachment modal.
  7. Verify the main composer will gain focus again.
  8. Make the main composer lose focus.
  9. Repeat step 3, 4, 5, and 6.
  10. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 4 (cancel file selection)

  1. Open a report.
  2. Focus the main composer.
  3. Click the plus button in the main composer to open the first attachment modal.
  4. Select the Add attachment.
    1. For mobile native platforms: select the Choose from gallery / Choose document.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click Cancel to cancel the file selection.
  7. Verify the main composer will gain focus again.
  8. Make the main composer lose focus.
  9. Repeat step 3, 4, 5, and 6.
  10. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 5 (send an attachment)

  1. Open a report.
  2. Focus the main composer.
  3. Click the plus button in the main composer to open the first attachment modal.
  4. Select the Add attachment.
    1. For mobile native platforms, select the Choose from gallery.
  5. Select an attachment.
  6. Verify that there is no focus/keyboard flickering during the transition.
  7. Click the top-left back button or Send button.
  8. Verify the main composer will gain focus again.
  9. Make the main composer lose focus.
  10. Repeat step 3, 4, 5, 6, and 7.
  11. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 6 (send an invalid attachment, e.g. file size < 240B)

  1. Open a 1:1 report.
  2. Focus the main composer.
  3. Click the plus button in the main composer to open the first attachment modal.
  4. Select the Add attachment.
  5. Select the Choose document.
  6. Select a document with a file ize less than 240B.
  7. Verify that there is no focus/keyboard flickering during the transition.
  8. Click the backdrop or Close button.
  9. Verify the main composer will gain focus again.
  10. Make the main composer lose focus.
  11. Repeat step 3, 4, 5, 6, 7, and 8.
  12. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 7 (attachment preview modal)

  1. Open a report with an image message.
  2. Focus the main composer.
  3. Click the image to open the preview modal.
  4. Click the back button or close button to close the modal.
  5. Verify the main composer will gain focus again.
  6. Make the main composer lose focus.
  7. Repeat step 3 and 4.
  8. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 8 (receipt preview modal + ThreeDotsMenu modal)

  1. Open a IOU report, which has a receipt image.
  2. Focus the main composer.
  3. Click the receipt image to open the preview modal.
  4. Click the ThreeDotsMenu button to open the menu modal.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click the backdrop or blank area to close the menu modal.
  7. Verify that there is no focus/keyboard flickering during the transition.
  8. Close the back button or close button to close the preview modal.
  9. Verify the main composer will gain focus again.
  10. Make the main composer lose focus.
  11. Repeat step 3, 4, 5, 6, 7, and 8.
  12. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 9 (receipt preview modal + ThreeDotsMenu modal + RHP)

  1. Open a IOU report, which has a receipt image.
  2. Focus the main composer.
  3. Click the receipt image to open the preview modal.
  4. Click the ThreeDotsMenu button to open the menu modal.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click the backdrop or blank area to close the menu modal.
  7. Verify that there is no focus/keyboard flickering during the transition.
  8. Select the Replace option.
  9. Verify that there is no focus/keyboard flickering during the transition.
  10. Close the backdrop or back button to close the RHP.
  11. Verify the main composer will gain focus again.
  12. Make the main composer lose focus.
  13. Repeat step 3, 4, 5, 6, 7, 8, 9, and 10.
  14. Verify the main composer won't gain focus again.
  • android native
  • android chrome
    controlled by useKeyboardManager
  • ios native
  • ios web
    controlled by useKeyboardManager
  • web
  • desktop


ThreeDotsMenu modal

case 1 (cancel action)

  1. Open a report.
  2. Focus the main composer.
  3. Click the top-right ThreeDotsMenu button to open the modal.
  4. Click the backdrop or blank area to close the modal.
  5. Verify the main composer will gain focus again.
  6. Make the main composer lose focus.
  7. Repeat step 4 & 5.
  8. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 2 (delete action)

  1. Open a IOU report.
  2. Focus the main composer.
  3. Click the top-right button to open the three dots menu modal.
  4. Select the Delete request to open the Confirm modal.
  5. Verify that there is no focus/keyboard flickering during the transition.
  6. Click the backdrop or Cancel button to close the Confirm modal.
  7. Verify the main composer will gain focus again.
  8. Make the main composer lose focus.
  9. Repeat step 4, 5, and 6.
  10. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 3 (waypoint editor, cancel action)

  1. Click the global FAB and select the Distance tab.
  2. Add three waypoints and then select one of them.
  3. Make sure the address input is focused.
  4. Click the top-right ThreeDotsMenu button to open the menu modal.
  5. Click the backdrop or blank area to close the modal.
  6. Verify the address input will gain focus again.
  7. Make the address input lose focus.
  8. Repeat step 4 & 5.
  9. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 4 (waypoint editor, delete option + cancel action)

  1. Click the global FAB and select the Distance tab.
  2. Add three waypoints and then select one of them.
  3. Make sure the address input is focused.
  4. Click the top-right ThreeDotsMenu button to open the menu modal.
  5. Selete the Delete option.
  6. Verify that there is no focus/keyboard flickering during the transition.
  7. Click the backdrop or blank area or Cancel button to close the Confirm modal.
  8. Verify the address input will gain focus again.
  9. Make the address input lose focus.
  10. Repeat step 4, 5, 6, and 7.
  11. Verify the main composer won't gain focus again.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

case 5 (waypoint editor, delete option + confirm action)

  1. Click the global FAB and select the Distance tab.
  2. Add three waypoints and then select one of them.
  3. Make sure the address input is focused.
  4. Click the top-right ThreeDotsMenu button to open the menu modal.
  5. Selete the Delete option.
  6. Verify that there is no focus/keyboard flickering during the transition.
  7. Click the Delete button.
  8. Verify that there is no focus/keyboard flickering during the transition.
  9. Add a new waypoint and then select it.
  10. Make the address input lose focus.
  11. Repeat step 4, 5, 6, and 7.
  12. Verify that there is no focus/keyboard flickering during the transition.
  • android native
  • android chrome
  • ios native
  • ios web
  • web
  • desktop

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (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
      • If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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 followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • 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
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • 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
    • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
      • 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(themeColors.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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop

@melvin-bot
Copy link

melvin-bot bot commented Oct 10, 2023

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@ntdiary
Copy link
Contributor Author

ntdiary commented Nov 29, 2023

Hi @0xmiroslav, when you get a chance, could you take a quick look at the implementation of this PR? It has successfully passed tests in many scenarios. I'm eager to get your initial impressions on this PR, such as whether this implementation approach is acceptable and if there are any serious blockers I might have overlooked. :)
Additionally, considering the importance of controlling the size of the PR, I am also planning to address some non-urgent cleanup tasks in follow-up PRs, such as removing unnecessary focus logic, optimizing the Modal implementation , and other improvements.

src/CONST.ts Outdated Show resolved Hide resolved
src/libs/ComposerFocusManager.js Outdated Show resolved Hide resolved
src/libs/ComposerFocusManager.js Outdated Show resolved Hide resolved
src/libs/ComposerFocusManager.js Outdated Show resolved Hide resolved
>
{props.children}
</View>
<ModalContent onDismiss={handleDismissContent}>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the purpose of this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

} else {
props.onModalHide();
close(props.anchorRef);
Modal.onModalDidClose();
}

It's somewhat similar to the above condition code, but has the following advantages:

  1. it's only called when the modal disappears (the code above is called even on the initial load),
  2. it's beneficial for extracting common logic in the future.

@@ -153,6 +154,7 @@ function WaypointEditor({route: {params: {iouType = '', transactionID = '', wayp
};

const deleteStopAndHideModal = () => {
setRestoreFocusType(CONST.MODAL.RESTORE_TYPE.DELETE);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the focus type have to change dynamically?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this case, when we remove a waypoint, the navigation will return to the distance page, the input is unmounted after refocusing is called, which can cause keyboard flickering. So setting the type to DELETE can avoid this issue. When clicking Cancel, we can set it back to DEFAULT to allow refocusing to continue working.

demo.mp4

@parasharrajat
Copy link
Member

I will take a deeper dive into this PR starting tomorrow.

@Julesssss
Copy link
Contributor

Hey both, just checking the progress here. It looks like there have been a decent amount of updates since the last review, but I see lint errors. @ntdiary is this ready for a second C+ review?

@ntdiary
Copy link
Contributor Author

ntdiary commented Dec 21, 2023

Hey both, just checking the progress here. It looks like there have been a decent amount of updates since the last review, but I see lint errors. @ntdiary is this ready for a second C+ review?

@Julesssss, so far, the current implementation has fixed many cases. My updates are more aimed at resolving conflicts.
I've also made adjustments based on the feedback from the previous review, so I think it's ready for a deeper review. :)

@ntdiary
Copy link
Contributor Author

ntdiary commented Jan 29, 2024

Just updated the test cases, so far, the count is 23. :)

Copy link
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @ntdiary, I didn't realise this would require so many test cases. Lets talk in the issue about increasing the bounty 👍

@parasharrajat
Copy link
Member

parasharrajat commented Jan 31, 2024

Yeah, I think the bounty should be increased for sure.

Meanwhile, we should create a project and put other focus-related issues on hold so that we don't create new challenges for this PR.

May be inform this on the C+ channel so that C+ can prevent that from happening.

@Julesssss
Copy link
Contributor

Hey @parasharrajat, bumping the review here now your back

@parasharrajat
Copy link
Member

parasharrajat commented Mar 2, 2024

I thought we are breaking this PR into parts. @ntdiary Could you please confirm?

  1. First PR phase1: fix emoji picker refocus issue #35572

@mallenexpensify
Copy link
Contributor

@ntdiary can you provide an update on where we're at here?
Asking cuz the below is held on this PR

@ntdiary
Copy link
Contributor Author

ntdiary commented Mar 29, 2024

@ntdiary can you provide an update on where we're at here? Asking cuz the below is held on this PR

@mallenexpensify, yesterday, @getusha reported two bugs in the first small PR #35572, and I'm still investigating them. :)

@Julesssss
Copy link
Contributor

Hey @ntdiary, just checking in here for the next steps as the linked PRs were merged.

@ntdiary
Copy link
Contributor Author

ntdiary commented Apr 29, 2024

Hey @ntdiary, just checking in here for the next steps as the linked PRs were merged.

@Julesssss, sorry for the delayed update. While I have reassigned all other new issues in the past few weeks, there are still two long-standing and relatively challenging issues that require my attention (#26239, #37596). Now that progress has been made on the other two issues, so expect to be able to raise a second small PR for this issue this week. 😂

@ntdiary
Copy link
Contributor Author

ntdiary commented Apr 30, 2024

image

It seems our app recently switched to the Fabric rendering system, which changed the execution order of some native & js code when displaying the modal. I'll investigate further this week to adapt to this new behavior. :)

@Julesssss
Copy link
Contributor

Ah another new problem introduced by the new architecture 😅

@Julesssss
Copy link
Contributor

Hey @ntdiary. Can we close this outdated PR?

@ntdiary
Copy link
Contributor Author

ntdiary commented Jun 17, 2024

Hey @ntdiary. Can we close this outdated PR?

@Julesssss, sure! BTW, I noticed that some issues have been put on hold because of this PR, so I plan to look into them this week to see if I can offer any suggestions, just like issue #31224. :)

@ntdiary ntdiary closed this Jun 17, 2024
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.

5 participants