@DTreserve Hm, then I don't know anymore.

@ryofurue Hi, yes it is a bit cumbersome you have to enable mail to get to this setting but you can disable it afterwards again. To my knowledge you have to disable the setting if the Vivaldi mail client is enabled and setup. It's maybe different when an extension is installed. If it work leave as is, you can remove the mail icon if it bothers you.

@luysx Hi, I guess the dev's simply forget to add it back to the new tab menu. You can add it back in Settings > Appearance > Menu Customization: [image: 1752038703430-69a543ca-c4f1-4c54-9fb0-ded29dc7b20e-image.png] Drag it to the left side.

@sgunhouse I'm not sure what that is supposed to do, but it didn't help. It's still beside the point and not the point of the thread. Google's AI overview aside, the actual issue I detailed persists with other search engines too.

@dovregubben Keep in mind that that system Chromium build's version is 136, while Vivaldi 7.5 is based on Chromium 138, so comparing what happens in the two might be like comparing apples and oranges (or as we Norwegians say (translated): apples and pears). I don't see any recent changes to the relevant Wayland related code, though, but there are quite a few changes in the general GTK wayland protocols code.

@shpankov: Верните как было! Я сам-то дизайнер на постоянке, что-то понимаю, но в ux дизайн долен быть как красив, так и функционален. Сделайте больше вариаций именно с иконками вообще (размеры)! Я ставил всегда их потому что все остальные варианты где видны превью сайтов это не интуитивно и перегрузка информацией. Ваш браузер лучший чуваки, люблю его и всем друзьям установил (не шутка), но не трогайте то что работает фор рил. Да я готов на созвон выйти с вашими дизайнерами и пояснить дотошно почему в десктопном приложении такой вариант не катит:) Только после этого на работу устройте)

@Shpankov, у вас такая будет экспресс панель или лучше?

@janrif Do you think anyone will help you without seeing the problem? Your screenshots don't show what you were asked for. Even with these settings, the "bookmark" button is still visible: [image: 933.png] Show the problem in the screenshot and provide a link to the exported theme: [image: 933.png]

@luetage Thanks very much for testing this out. I just tried installing Vivaldi on a separate computer just to see the default behavior. On the tab bar on the left there are three default "web panels", one for Vivaldi Social, one for Vivaldi Help, and one for Wikipedia. These all seem to work as expected; I can open and close them, and Vivaldi leaves them closed after restarting. I've been using Vivaldi for a few years without any significant issues, but as I mentioned this problem started a few days ago when I opened the Help panel. After that, every time I started Vivaldi the panel opened. I eventually deleted Help and Wikipedia from the panel strip, and between that and fiddling with closing Workspaces the problem has gone away. If it happens again I'll try to collect more details and post another question.

@GamingSKITZ said in Whats your favorite game?: Im just curious as what yalls favorite games are Mario for me S 6 Replies Last reply 28 Oct 2024, 07:29 Reply My favorite games are Free Fire and PUBG very interesting survival shooting games

Redfox777さんと同様の挙動が発生しています。 新しいプロファイルでテストを行いましたが、同じ現象が発生しました。 また、再インストールも試みましたが、正常にはなりませんでした。 [image: 1752023246503-wwwyoutubecom4793553cbff9.png] youtubeにてピクチャインピクチャを使用後、ピクチャインピクチャを解除。 すると、添付画像のような状態になります。

@lengjian I wasn't able to find that thread until after I submitted this post, so I apologise for that, but interestingly enough, yours has a third VB code. VB-86526 was the one I found initially, VB-89876 is the one mentioned in your thread, and VB-95233 is the one mentioned in this thread. Which makes me wonder if they are similar (but different) issues, or just duplicates. I know a public issue tracker is not going to happen (and I understand why), but it'd be nice to know if these are related, when they were opened and their priority number. English is my second language, and this is an incredibly useful accessibility feature. For now I've been relying more on Spotlight (by copy-pasting the word), but it's more convoluted (and thus, way less efficient) than just force-clicking. I wouldn't be surprised if this bug has a low priority number, as with any accessibility-related feature, it's only a niche that needs them. It's understandable, though, Vivaldi's a small team and the browser has a relatively small user base, so this bug affects a niche of a niche. But I'd be interested to know the status (including the priority number) of these three VB codes (mostly the last one (VB-95233) as that was the one mentioned in this thread), as that version you mentioned is quite a few years old.

@vivaldio9acx Said: The worst piece of software I've ever used Don't suffer any longer.

7.5 breaks this in two ways: Text in focused window is visible "+" button is now managed by dynamic element-style so there is no approach to fix that with a custom CSS for problem 1: append this to the custom CSS: .tab.active.button-off .title { display: none; } for problem 2: depends of what you want: /* uncomment this if you want the + button (bugged) */ /* .tabs-top #tabs-container .resize, .tabs-bottom #tabs-container .resize { margin-right: -48px; } #tabs-container .resize { position: static; pointer-events: auto; display: initial; flex: 0 1 auto; overflow: visible; } */ /* uncomment this if you DON't want the + button */ /* #tabs-container .toolbar-tabbar-before > div > .button-toolbar > button, #tabs-container .toolbar-tabbar-after > div > .button-toolbar > button, #tabs-container .toolbar-tabbar-before > .button-toolbar > button, #tabs-container .toolbar-tabbar-after > .button-toolbar > button { display: none;} */ /* This was supposed to put the + button before the window buttons, but the button is broken :(*/ /* #tabs-container .toolbar-tabbar-before > div > .button-toolbar > button, #tabs-container .toolbar-tabbar-after > div > .button-toolbar > button, #tabs-container .toolbar-tabbar-before > .button-toolbar > button, #tabs-container .toolbar-tabbar-after > .button-toolbar > button { position: fixed; right: 6vw; top: 0vh; } */ so the final full CSS would look like this (i prefer to not have the bugged "+" button): /* uncomment this if you DON't want the + button */ #tabs-container .toolbar-tabbar-before > div > .button-toolbar > button, #tabs-container .toolbar-tabbar-after > div > .button-toolbar > button, #tabs-container .toolbar-tabbar-before > .button-toolbar > button, #tabs-container .toolbar-tabbar-after > .button-toolbar > button { display: none;} .tab.active.button-off .title { display: none; } /* Fix the tab position by removing transforms and changing the position type */ .tab-position { transform: none; position: relative; display: flex; flex-direction: row; height: 30px; width: 30px; z-index: 0; } /* Fix the direction of the tab container */ #tabs-container .resize .tab-strip, #tabs-container .resize .tab-position, #tabs-container .resize .toolbar-tabbar { pointer-events: auto; display: flex; flex-direction: row; left: -25px } /* Fix tab name overlapping with other tabs */ .tab-position .tab.active, #tabs-container .tab-position .tab.tab-accordion, #tabs-container .tab-position .tab.tab-first-in-group { overflow: hidden; } /* Fix the new tab button by removing the X position calculation */ .tabs-top .toolbar-tabbar .newtab, .tabs-bottom .toolbar-tabbar .newtab { --PositionY: unset !important; left: unset !important; }

[image: 1752015072980-sd_-elevenforum.com.png]

@HeinoKramm said in Integrate Private Tab Access and Possibly Other Features into the Vivaldi Widget: @ThePfromtheO It’s a great idea, but I think requesting that would make it even more complicated for the Vivaldi developers to implement. True! But it doesn't hurt to request it. It's clear at this point they are already interested in doing complicated stuff as long as it makes sense and aligns well with their vision. I mean I'm already fairly positive patching in a notepad (and modifying the sync mechanism to support said notepad) altering a significant portion of the browser UI and patching in a adblocker was likely significantly more complex then this would be. They can decide for themselves whether they can handle it or not and if they can't well they can just focus on adding a proper shortcut to the widget. So I'd say don't worry about it too much. As long as they are aware of both possibilities they'll likely chase after the option that makes more sense and is more feasible for them to do.