Skip to content

Refactor find in page state #5926

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

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

LukasPaczos
Copy link
Contributor

wip

@LukasPaczos LukasPaczos force-pushed the feature/lukasz-p/update-find-in-page-design branch from d5b432d to a5a96b2 Compare April 17, 2025 15:10
Base automatically changed from feature/lukasz-p/update-find-in-page-design to develop April 17, 2025 19:37
LukasPaczos added a commit that referenced this pull request Apr 17, 2025
Task/Issue URL:
https://app.asana.com/1/137249556945/project/1208671518894266/task/1209874980847232

### Description

The "find in page" state is currently fully managed by
`BrowserTabViewModel`. This PR makes the omnibar aware of the visibility
portion of that state - just enough for it to react and pass it down to
its children.

Functionally, there’s no change for the production omnibar. But in the
experimental omnibar - where the "find in page" UI is moved inside the
card - we can now detect when it’s shown and hide other content
accordingly. This lets us reuse the omnibar card’s existing design and
animations.

This PR keeps the changes minimal, focused on adapting "find in page"
for the experimental omnibar. As a follow up, in
#5926, I'm attempting to
migrate the whole of "find in page" state management out of
`BrowserTabViewModel` and into the omnibar, along with further cleanup.
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.

1 participant