@Gra1g

7fa584de-1f50-4d9c-a6b2-2e892115c0c1-image.png

https://forum.vivaldi.net/category/136/mobile-feature-requests

Vivaldi version Android 6.6.3291.89
Happening since yesterday.
OS Android 12
Device Samsung 51

Hi,
I face the same issue on my Huawei P30 Lite, and it is very annoying.

I tried changing the screen resolution as @mib2berlin and @jstressman mentioned. It didn't work ( I have 3 screen resolutions: smart, high, and low, the annoying weird bottom bar on top of the status bar stays in all of them).

I tried to activate and deactivate the address bar at bottom (my address bar is usually on top) as @ipan12 suggested: when the address bar is at the bottom, the annoying bar disappears, and actually, I think I might like having the address bar at the bottom, so I'll give it a try.
However, when deactivating the bottom address bar, the annoying bar reappears.
So the problem is still there.

To reproduce the issue, I have a Huawei P30 Lite, running on Android 12.
I hope that it will help the Vivaldi team to solve the bug.

@skyisthela

Do not misconsider Devs
For whatever reason isn't fixed yet.

You can use a Desktop to manage it in the meantime.

@jane-n This bug started a few releases before Vivaldi 6.6 was released

The steps to make the bug happen are random (I think), and these are the three ways I've found to reproduce the bug.

Click on the search bar and type in a word, then click on a link that is saved in the bookmarks. Click on the search bar and type any word And accept. Open a new tab and on the Speed Dial , click on a web page.

The first option is more common for the web page to be displayed in black/white. And the third option is a bit frequent.

When the screen is black/white, it doesn't matter to reload the web page, it will remain the same. In order for the web page to be displayed correctly, all you have to do is change the tab and it will be displayed.

I've been using Vivaldi Snapshot 3335.22, It also has the white/black screen issue, but it's much less prevalent than previous versions including the stable version.

Sorry if I have bad spelling, I'm using a translator to translate the text from Spanish to English.

Yes, it is a bug. Luckily, it has already been fixed and will reach the Stable version with the next update.

@Maverick3k
Hi, the actual 5 seconds are to long for the most user and you can open it again with Edit Bookmark in the menu.
If you like a setting for this create a feature request.
If I set "Show toolbars while scrolling" they never disappear.

Please, always add your Vivaldi, Android version and your device.

https://forum.vivaldi.net/category/136/mobile-feature-requests

Cheers, mib

@mib2berlin Thanks there.

So that thread covers all Desktop, Android versions, right?

Thanks. I appreciate it

New problem:) !
It turns out that the switch "Enable zoom" does not have a special effect . If the zoom is selected in the 5-seater menu, the state of the switch does not affect the display of the zoom. There is always zoom.
This switch is not needed. Turn on the item "Default zoom" constantly. Make it an equivalent menu item. There is no point in highlighting it.

@CADutchman Please submit a bug report here. Include all relevant information and include screenshots where applicable. Thank you for helping make Vivaldi better.

@mib2berlin said in Forward and back buttons:

I don't use AB at bottom but you can use swipe left and right for this.

Probably, I know what you mean. But these gestures are very difficult to implement in Vivaldi. If system-wide gesture control is enabled in Android, you get overlapping and complete confusion. And on this forum, there is triple overlap. See the screenshot - I made it on Kiwi, it is very difficult to even catch it on Vivaldi!

This is an old, but very interesting problem to solve - how to make gesture control in Vivaldi more convenient! Given all this complexity.

IMG_20240419_155518.jpg

btw. this post inspired me to add a reading view to my Dialog Mod as well 😉

It might be useful to say where you got the instructions from – people then might have a better chance of assisting you with any problems – and also to state exactly what you observed/what went wrong (rather than "I failed to adapt these commands").

I posted one version of these in an answer on Android StackExchange, here:

  https://android.stackexchange.com/questions/56635/how-can-i-export-the-list-of-open-chrome-tabs/199496#199496.

Those commands do work for me with Vivaldi for Android version 6.5.3217.103. However, it's always possible that Vivaldi, or any other chromium-based browser, might disable or remove this method of debugging in the future (Brave has considered doing so).

As mentioned in my StackExchange answer, you can check what Unix domain sockets exist on your phone by running adb shell cat /proc/net/unix. If your browser is running, but a socket named @chrome_devtools_remote isn't in the list, then your browser simply doesn't support this method of debugging. (I'm not sure what happens if you have multiple chromium-based browsers open on your phone at once – do they all try listening and writing to the same socket? Perhaps so.)

Another possibility is that curl might initially output an empty JSON list ([]). Occasionally I've had that happen, but it seems to be an intermittent error, and waiting a few seconds and trying again has retrieved the full list of tabs.

I was able to reproduce the crash on the Stable version, but can't reproduce it in the Snapshot version of Vivaldi, so it must have been fixed. All there's left to do is wait for an update to the Stable version.
Thank you for your patience. 🙂

@Chipy
Hm, which device and Android version do you use?
You can report it to the bug tracker, I cant confirm but we have many testers with almost all devices.

For information on how to report a bug, see this URL: https://help.vivaldi.com/article/report-a-bug-in-vivaldi-android/
Once that is done, please share the bug number (beginning with VAB-). Thanks.
On the form, you can add your email address. Once submitted, you'll get a confirmation. You can reply to this with any logs or further info.

Cheers, mib