25
Embedded links no longer working?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Sep 2023
25 points (93.1% liked)
Jerboa
10133 readers
19 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
- Open source, AGPL License.
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
- bitcoin:
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK - ethereum:
0x400c96c96acbC6E7B3B43B1dc1BB446540a88A01 - monero:
41taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuV - cardano:
addr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
Contact
founded 2 years ago
MODERATORS
The changelog says "Support private tabs for FireFox by @dankeast in https://github.com/dessalines/jerboa/pull/1216" but OP mentioned Chrome...
Also it's somewhat broken on Firefox. If you leave the tab open and go to the homescreen, the next time you open Firefox it will start in incognito mode which drove me nuts. Also some pages won't load properly in Firefox in incognito mode (looking at you, imgur).
While I like the idea, I don't think it should have been enabled by default with an update, as I cannot remember setting this manually....
In case someone else is searching for this setting, its "use private tabs"
It didn't enable by default in this update. But I think when it did get added it was with default enabled but that was a while ago. I can take look at changing this default.
That issue with firefox is not one caused by Jerboa. So that would need to be reported with FireFox. The only change we did was add support for FireFox.
Thanks for the clarification- that means it was probably active for a while, but didn't work for me and I was only hit by it now, because now my browser is supported.
It's entirely possible, that I enabled that setting a while ago and forgot about it (or maybe accidentally) and never noticed that because of using Firefox.
I know, that the behavior of Firefox is likely not caused by you. I'll experiment around a bit and try to reproduce it reliably before filing a report there