JaddedFauceet @ JaddedFauceet @lemmy.world

Posts

0

Comments

68

Joined

2 yr. ago

joke aside, story point can be quite arbitrary

last breeding with a neanderthal

npm ruin dev

npm ruin lint

npm ruin build

As a web app, such behaviour will also need to be programmed to work on a browser first. Packaging it for Play Store should not grant that behaviour automatically.

(2) Image overlay For Voyager, back button for image overlay works in browser.

When opening an image viewer, the web app triggers a browser history change like this:

1. Browsing on feed - https://vger.app/posts/lemmy.world/all
2. Opening an image viewer - https://vger.app/posts/lemmy.world/all#galleryOpen

^ notice the extra #galleryOpen

When back button is triggered, the web page will listen to a "back" event, and close the image viewer.

(3) Keyboard: Keyboard is a native UI. So triggering "back" will always close the keyboard

(1) Modal / bottom sheet

But... I couldn't figure out this one yet

Clicking on the "3 dots icon" in a post opens a bottom sheet interface.

Play Store version response to back button properly. But the web app version does not.

I installed it as a web app earlier. I don't recall conflict with back gesture. What's the issue with back gesture?

Do you expose your DNS server to the public? If not how do you use it outside of the network? Like on mobile

From my understanding, the fdroid process ensures the build is automated base on the source code provided. This prevents developer from sneaking in additional code in the build.

Wait... hosting on tor is free?