Privacy Browser Android

My experience is that this is actually on of the WebView bugs introduced with Android 14. Specifically, it appears to be something to do with the way the WebView is processing inputs. It tends to affect some websites much more than others, lending me to think it might be related to the JavaScript that is being processed. For example, I personally find it happens a lot with https://www.deseret.com/.

When I experience this problem it is often after a scroll event is incorrectly detected as a fling, which is then over processed (it scrolls massively fast to the bottom of a page). After that, it doesn't process touch events correctly (long-pressing on a link doesn't pull up the context menu). Of all the thing I have tried to fix this, the only thing that has worked so far is moving the WebView off the screen by switching to another tab and then switching back. My guess is that a bunch of logic is run whenever the view is hidden and then redisplayed that corrects whatever has become confused in WebView's touch processing.

There doesn't appear to be anything I can do to fix this problem, but I expect Google to fix it in a future WebView update. It might be fixed at the same time as Bug #1106: New intents sometimes aren't loaded on restart on Android 14 (WebView crash). They might even have the same underlying cause.

Yes this is the recent issue I've been facing. On both FOSS Browser & PB. But FOSSB prioritises context menu before drag & dropping links. Here in PB, it turns into drag n drop instead of context menu.

I'm not sure what you mean by drag and drop.

When the 2nd trial for bringing context menu, that's where it turns into another feature where you can drag & drop the link to some other place. I believe this has to do something with tablets or a desktop browser thing.

That's interesting because it is not how my device behaves. Regardless, it appears to be fully a problem with WebView than can only be fixed by an update to their code.

That's interesting. It's not how my device behaves. If I thought there was something I could do about it I would try to narrow down why it is different for you than for me, but because I can't do anything about it I would rather spend the time on more fruitful endeavors.

Sure. Don't worry about this I guess. If it's webview issue I think it'll get fixed by itself on further updates.