Vivaldi doesn't respond to touch input [workaround]

asked 2019-12-25 20:56:09 +0200

Direc
5243 ●104 ●149 ●149

updated 2019-12-25 21:10:53 +0200

Hello,

I have been using Vivaldi (beta 2.9 just now) for Android for a while now with great user experience, go give it a spin! However, I always eventually ran into situation where the browser comes often completely unresponsive. It "fixed itself" by reinstalling the app, or by clearing all user data. I did some bried testing and got some results.

Edit 1: I forgot to mention that the browser becomes unresponsive when the URL/search bar is touched. Browsing the already opened page works just fine.

Vivaldi (almost always) stops responding to touch input at least when these conditions are met:

• Google is set as the default search engine
• Vivaldi is given the permission to use location in Android settings
• Google is not allowed to use location in Vivaldi settings

Edit 2: This doesn't occur with Yahoo! search engine as default with the same location settings, which indicates a bug in Google search engine implementation, or in Vivaldi.

I am not completely sure if all the three are required, but that is how I manage to get the unresponsiveness to occur. To make the browser work well, at least the following works:

• Disallow Vivaldi from using location in Android settings

My wild guess is that Google (or other search engine?) asks for location, Vivaldi then asks it from Android, doesn't get a proper response (or no response at all?) and gets stuck in a loop.

I haven't seen Sailfish location symbol getting activated when the hang occurs. I'm not sure where the bug is, but I assume people using Google with location disabled is quite common, and because this bug has bugged me over many releases, I think it's in aliendalvik and related to location.

Here are the rest of the details:

• Sony Xperia XA2 Ultra
• Sailfish X 3.2.1 EA
• Vivaldi Browser 2.9.1741.39.417410039
• microG services core 0.2.10.19420
• MozillaNlpBackend 0.1.0 (doesn't help nor hurt)

This question is less of a bug report and more like a "hey I found a workaround" but anyway, if someone has a clue about what's really going on, any information is greatly appreciated.