-
Notifications
You must be signed in to change notification settings - Fork 68
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
Custom tabs does not respect default browser #143
Comments
Hi @hjiangsu, Thank you for reporting this issue.
This is intended behavior and not a bug. It was fixed in It is possible to add an option to |
Thanks for clarifying the issue.
Having the option to prioritize the default browser would be great! |
Got it! I will add an option to |
Hi, I've just published the new version This release includes a new option, await launchUrl(
...,
customTabsOptions: CustomTabsOptions(
browser: const CustomTabsBrowserConfiguration(
prefersDefaultBrowser: true,
),
),
); |
Thank you for the update! I'll test it out when I have the chance |
@droibit Thank you so much for the super fast response on this issue! It'll really help us out. Purely out of curiosity (no judgement), was there any reasoning for the intentional change to prefer Chrome? Thanks again! |
@micahmo I originally made the decision to prioritize Chrome because at the time of development, Due to this limitation, the decision was made in |
Version |
Issue
Custom tabs prioritizes Chrome over the default browser's custom tabs. When setting a default browser with support for custom tabs (e.g., Firefox), triggering custom tabs will attempt to open the custom tab in Chrome. Only when Chrome is disabled, custom tabs will open using the default browser's custom tab.
To reproduce this issue:
Expected result
Custom tabs should open using the system's default browser if the default browser supports custom tabs.
Notes
This seems to happen both on the latest version
1.2.1
and the latest beta2.0.0-beta
The text was updated successfully, but these errors were encountered: