Bug search in page function closes itself
-
This is a really strange bug and I post this to make sure I am not the only one getting this.
Go to https://forum.vivaldi.net/topic/13217/feature-requests-for-1-7/402because the request site is literally the only site where this happens so farPress F3 and search for a word that exist on this page (I used tab, clear, private and a few usernames)
After a few seconds of not pressing enter or hovering the mouse over the search bar it just disappears. I have to recall it via F3 just to see it disappear again after 2-15 seconds.Rest of the Forum seems fine so far and I couldn't find any other website to reproduce this.
Can anybody confirm this?
EDIT: This happens all over the forum on threads that have so many answers that you have to scroll. So this might be forum related and not vivaldi related.
Btw: win 7 64-bit with viv 1.7.735.11 32-bit
-
@zaibon I've just replied to another user considering a similar bug, so here is my comment:
I think it's a known bug, though to reproduce it on this forum you have to turn off the "Paginate topics and posts instead of using infinite scroll" option in settings. It is also related to dynamically created content and websites that use AJAX or just the JavaScript to create or modify the content of a page without reloading it.
As I said, the search feature still requires some polishing and fixes, so if you have any bugs to report you can always do so by filing a bug report.
How to do a bugreport for Vivaldi:
Please describe as precisely as you can and report the bug at https://vivaldi.com/bugreport/.
You will get a bug confirmation mail and in a reply to this mail you can add more information and files as attachments for the testers and bug tracking team.
Thanks in advance.
-
The thing that occurred strange to me is that I just yesterday (before installing the latest snapshot) searched in the feature request thread and everything was fine. Today with no changed settings this happens
I'll test it a bit further and file a bugreport after work or tomorrow
-
EDIT: For me this bug disappeared with the update to 1.8.755.3
-
-