-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Split Omnibar: Address bar integration #7042
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
Conversation
09fe074 to
b658d9f
Compare
6a5cb77 to
539390e
Compare
1837d54 to
34b46fd
Compare
539390e to
697f6fb
Compare
065ac0e to
7b19df7
Compare
malmstein
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let’s avoid creating more flags that duplicate what’s already existing.
| private val _viewState = MutableStateFlow( | ||
| ViewState( | ||
| showChatMenu = duckAiFeatureState.showOmnibarShortcutInAllStates.value, | ||
| showButtons = settingsDataStore.omnibarType != OmnibarType.SPLIT, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is already a showTabsMenu, showFireIcon and showBrowserMenu, why not use those instead? showButtons is not really clear what it means
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I’d use the existing flags to decide if the container needs to be shown or not. Bonus points if doing that also prevents the Transition in renderButtons to run if the buttons are not visible.
| * If the remote feature is not present defaults to `false` | ||
| */ | ||
| @Toggle.DefaultValue(DefaultFeatureValue.FALSE) | ||
| @Toggle.DefaultValue(DefaultFeatureValue.INTERNAL) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be false by default, otherwise you’re turning this on for all internal users
| binding = binding, | ||
| isUnifiedOmnibarEnabled = omnibarFeatureRepository.isUnifiedOmnibarFlagEnabled, | ||
| ) | ||
| configureNavigationBar() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what’s the reason for this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To initialize the navigation bar earlier and reduce the flickering when loading. It helped a bit but did not fully work. I found the actual reason, so reverting (not that it really matters).
|
@malmstein Thanks. Ready for another round. |
e25a604 to
643feee
Compare
7ebd273 to
b136ce0
Compare
malmstein
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
works great, thanks @0nko !

Task/Issue URL: https://app.asana.com/1/137249556945/project/1207418217763355/task/1211565479656355?focus=true
Description
This PR adds the last integration of the split omnibar to the address bar:
Steps to test this PR
Omnibar button
splitOmnibarflagMock split toolbar