Skip to content

Conversation

@m-abs
Copy link
Collaborator

@m-abs m-abs commented Jun 13, 2025

  • feat: moved into a wrapper fragment class
  • new fragmenet is now used
  • fix: fragment init must be without arguments

@m-abs m-abs requested a review from ddfreiling June 13, 2025 11:49
Copy link
Member

@ddfreiling ddfreiling left a comment

Choose a reason for hiding this comment

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

Code LGTM, need to test.

return false;
}
// Checks also that the locator also contains `active` class.
// TODO: This doesn't do what we expect, if the range is visible but not active, this function will return false.
Copy link
Member

Choose a reason for hiding this comment

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

We actually fixed this on the lyt4 branch, we need to backport it here.

Copy link
Member

@ddfreiling ddfreiling left a comment

Choose a reason for hiding this comment

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

Awesome job 🚀

Minor readability comment.

it.locator = initialLocator
it.preferences = initialPreferences

it
Copy link
Member

Choose a reason for hiding this comment

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

This use of let hurts readability.

@ddfreiling ddfreiling merged commit 13758cf into main Jul 2, 2025
@ddfreiling ddfreiling deleted the fix/android-crash-fragment branch October 30, 2025 08:27
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.

3 participants