this post was submitted on 01 Aug 2024
14 points (100.0% liked)

Jerboa

10300 readers
2 users here now

Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.

Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.

Built With

Features

Installation / Releases

Support / Donate

Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.

Crypto

Contact

founded 2 years ago
MODERATORS
 

For me, both of those functions open the link in the built-in browser. Is this a common problem?

all 5 comments
sorted by: hot top controversial new old
[–] [email protected] 7 points 3 months ago* (last edited 3 months ago) (1 children)

Do you have the app internal browser (custom tabs) enabled? Open link shows it in the app browser, open link external pops it open in firefox.

I suppose we could make a request to hide the 'open link' option from the list if the custom tabs feature is disabled? Perhaps we could also include a tooltip for the custom tabs feature to convey that is works as the in-app browser.

[–] [email protected] 2 points 3 months ago (1 children)

so it was initially enabled. now that i disabled it, it always (both with open link and external) opens links in firefox. not the behavior i would have expected, but this is fine since I mostly want links to open in firefox anyway. thanks

[–] [email protected] 2 points 3 months ago* (last edited 3 months ago)

Oh sorry I misread, so it always opened internally regardless of that setting? That could be worth a bug report on their repo if you have the time (and can reliably reproduce the behaviour). Could be a quirk with Firefox for Android as well, though.

[–] [email protected] 2 points 3 months ago

Try on a shared image. One should open in the app, the other in the browser.

Perhaps there will be an internal Webview implementation one day.