@BigBrothyr No problem here. Specs: AMD A10-6800K, 8 Gb on Win 10 64-bit 1809 build 17763.316 • Snapshot 2.4.1455.4 (64-bit)

Standardowo nie ma ustawionego do tego skrótu klawiszowego. W ustawieniach karty>pokazuj pasek kart. Jeżeli skrót jednak jest przypisany to w ustawieniach: klawiatura>widok>pasek kart

@CryptisMidnight In fact what you did already was the correct way that you don't have to disable bitdefender in the future, as the blocking is coming from their site the Vivaldi devs can't do much about it so the only way is to let bitdefender developers know about the problem - the more people do this the more likely it is that they'll test their new versions against vivaldi before releasing it. So a big thanks to you for contributing

The problem continued this morning so I rebooted, opened TM found no Vivaldi in running processes. Opened Vivaldi then exited, waited a minute or two, opened TM and 2 Vivaldi running in processes. Ended those processes (luckily it worked for me), closed TM and opened Vivaldi again...then exited, checked and both were back. I opened Chrome, to see if something similar was happening with that browser, then exited, checked and no Chrome in processes. BUT...very odd....the next time I opened Vivaldi and exited, then checked Task Manager, all instances of Vivaldi in running processes were gone and things appear normal in that regard. Now just need to check it with my research site to see if notes and changes will be applied in this snapshot.

Nope, problem still exist.

It's working for me too. I just hope the next time Google does an update it doesn't bork things up again concerning this issue.

@Gwen-Dragon I'm thinking about some not-too-complicated process, like // the bug needs to be properly indexed in the database first function CheckBugsDatabase("SomethingDoesn'tWork") { var TheBug = get BugReport("SomethingDoesn'tWork"); var duplicates = CheckForDuplicatedReports(TheBug); // checking if it was already reported if (duplicates>"x") { // if it was reported at least "x" times var bugData = getBugBasicData(TheBug); // get the basic info about the bug exportToTheList(bugData); // send it to the "known issues" list } else if (duplicates==0) { // if it wasn't already reported saveToBugReportsDatabase(TheBug); // just save it to the database } } // this is just a primitive example of how it could be done, it's not an actual code This is pretty much how I imagine those companies doing their "known issues" lists. I mean, it's obviously doable. "Where there's a will, there's a way"... 😉 @Gwen-Dragon said in A place for a "Known Issues List" of the current stable release of Vivaldi: (...) It is not a easy-to-do-i-5-minutes job to filter information which should not go into public. (...) I think that the "reported x times" condition is good enough for that matter. If an issue has been reported at least several times, there's a pretty good chance that it's already been made public somewhere on the forums or on the team blog. But they can always decide not to publish a certain bug report - despite it's being reported frequently - for any reason. And they should obviously publish only the most important (from a user's perspective) information about the bug (like what it causes and whether it's fixed already or not just yet), not the whole report and technical data (especially if it's a security flaw or something like that). @Gwen-Dragon said in A place for a "Known Issues List" of the current stable release of Vivaldi: (...) that all this public list would bind too much human power which would be better invested in more features and bug fixing. ... and managing duplicated bug reports. 😉 PS. By talking about "thousands" of bugs, you look to me like an optimist. 😁