[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Open in In-app Browser #406

Open
issuant opened this issue Jul 1, 2024 · 4 comments
Open

Open in In-app Browser #406

issuant opened this issue Jul 1, 2024 · 4 comments
Assignees
@1fexd
Labels
g/custom-tabs g/customization-overhaul t/feature-request

Comments

@issuant
Copy link
issuant commented Jul 1, 2024 •
edited
Loading

Feature description

Can we have an option to, where possible, open links the in-app browser of the app that triggered Linksheet?

An example would be if you tapped a Wikipedia link while browsing a subreddit in the Reddit app and it brings up Linksheet, it would be nice to be able to have an option to open it in the in-app Reddit browser instead of the full default browser.
@1fexd
Copy link
Collaborator
1fexd commented Jul 1, 2024

Is using the "Force disable in" option in the in-app browser settings not an option?

@issuant
Copy link
Author
issuant commented Jul 2, 2024

I actually have what might be a bug to report about that but what I am asking for here is to (have the choice to) enable the in-app browser in some cases which is the opposite of what 'Force disable in' does.

Currently, the only way to achieve this is to switch my default browser from Linksheet back to Brave but, aside from that being not the greatest UX, it causes another issue as seen in #405.

@1fexd
Copy link
Collaborator
1fexd commented Jul 2, 2024

I actually have what might be a bug to report about that but what I am asking for here is to (have the choice to) enable the in-app browser in some cases which is the opposite of what 'Force disable in' does.

Oh, yeah - never bothered to implement that 😆

@1fexd 1fexd added this to the 1.0.0 milestone Jul 2, 2024
@issuant
Copy link
Author
issuant commented Jul 3, 2024

Great. I don't know what the initial plans about the implementation was but it would be great if this was accessible per link as an option via the bottom sheet rather than fixed in a sub-menu like the current 'Force disable in'.

@1fexd 1fexd added this to Issues Sep 18, 2024
@1fexd 1fexd assigned 1fexd and unassigned 1fexd Sep 18, 2024
@1fexd 1fexd removed this from the 1.0.0 milestone Sep 23, 2024
@1fexd 1fexd moved this to Backlog in Issues Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@1fexd 1fexd

Labels
g/custom-tabs g/customization-overhaul t/feature-request
Projects
Issues
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@1fexd @issuant