Vivaldi Forum mod
-
@luetage Seeing as there's now a default "inline code" button, I'm changing the button that makes
this
into a Fixed Width Font button, using the other icon. That will need translating. β -
Stylish theme has been updated after the forum update, fixing mainly the header. Sorry that I haven't had a chance to get stuck into your mod yet @luetage, too busy.
-
Argh, here we go again, (seemingly) arbitrary div renaming. And I was almost done fixing up my themes which needed a little attention anyway... I'll make the changes and submit them as well as the compact header mod which I was running at the end of my themes since I use them in stylus, but I can't promise an ETA.
-
I reverted the master branch back to 1.64 and started submitting fixes. Doesn't look like we'll get the themes ready, but everything else should be doable in short order.
-
Wow, I tried the new version of the forum with VF Mod disabled to see the changes (which are nice) but I can truly say I can't live without VF Mod at all... I understand your frustration @luetage but I just want to thank you again ( @LonM and @wiiija included of course - and other contributors that I could not know) for what you've offered to us. It really has an added value on a daily basis!
-
@luetage What a coincidence... I was writing a thank you message to you guys while you were around
-
//EDIT: This code is quite "old" now. Kept for nostalgic reasons only ^^,
#vivaldilogo img {filter: invert(.8);} #vivaldiheader {background: #333;} #submenu {background-color: #333;} #submenu li>a:hover { color: white; background-color: #555; } .emoji-tabs {background-color: #555;} .emoji-dialog .top-bar {background: #555;} .nav-tabs>li.active>a, .nav-tabs>li.active>a:focus, .nav-tabs>li.active>a:hover { color: white; background-color: #333; } #vivaldifooter a {color: white;}
-
@luetage said in Vivaldi Forum mod:
I'm also pretty pissed right now
In Oz that'd simply mean you're drunk. Conversely when we're annoyed, we're pissed off.
-
@Hadden89 I wouldn't be so sure about that. I finished the fixes for the modifications redid default fixes. Right now I'm in the middle of doing the custom theme. Don't think I will be finished anytime soon. And you heard @wiiija, he is busy right now. So sprucey won't be fixed I guess and @sjudenim gave no ETA. Therefore the next release will probably only have the mod theme and custom themes ready.
-
Version 1.65
This is a release of fixes. All modification regressions have been fixed and the default forum fixes have been reworked. The only completely fixed theme is the custom theme option, but this one is really finished. I suggest you either use a custom theme or choose the standard theme option for the time being. At the moment we can't tell if and when the other themes will be updated too.It's too hard to list all the changes, it's been a lot of work. I want to thank @LonM for reacting quickly and bringing the advanced formatting mod up to speed again. Sorry for the theme situation, but I'd really suggest you try out the custom theme option. You can download following zip with premade themes and import them into the options page.
custom-themes.zip (download)
-
You can force the update with developer mode on Vivaldi's extensions page now, the update seems to be up on webstore. Good night/morning.
-
@luetage said in Vivaldi Forum mod:
bringing the advanced formatting mod up to speed again
Just on this point, the emoticons are now under a
β₯
symbol, so that it doesn't get confused with theβΊ
for the emoji.Also, I tried to avoid any of the toolbar icons getting moved around too much during the update. Let me know if anything goes seriously wrong there, but at most only the
βΊ
andβ₯
symbols should be in different places.edit: boi, dont emojify my already unicode symbols
-
-
-
A notice to all who want to put work into their themes. Vivaldi made 3 significant changes in the header.
-
First of all the new menus, which have to be styled separately, they're not normal dropdown menus and shouldn't be treated as such.
-
The Vivaldi logo is new and has different dimensions. Additionally it isn't transparent anymore, it has a white background. I made 2 new logos from it which are transparent β
logo-white.png
andlogo-black.png
, you can use these for your own themes. The old way of changing icons I introduced doesn't work anymore, the code has to be adjusted. Example for dark themes:
#vivaldilogo { background: url('chrome-extension://__MSG_@@extension_id__/themes/img/logo-white.png') no-repeat; } #vivaldilogo img { display: none !important; }
- The new down arrows (carets) which indicate the menus are an image loaded from Vivaldi's servers, just like the logo. This is a problem, because we can't theme them. I don't know why they used an image, because the same caret can be found in FontAwesome. I exchanged the pictures for the FontAwesome equivalent as new default mod in the extension and you can't really tell a difference, it's very close. The only thing you have to do is prevent them from changing their color on hover, like so:
#vivaldimenu a .sub-arrow::after { color: var(--colorFg) !important; }
Exchange
var(--colorFg)
for the standard foreground color of text in the header.I hope this helps a little. It's at least things I struggled with.
-
-
version 1.66
- Theme Mod and Sprucey Bonus Dark updated β they should be working fine now.
- A plethora of additional fixes and adjustments, for example the account, groups and content margins should be working perfectly now on all screen sizes.
What's missing is DarkGrey and LightGrey, but afaik @sjudenim is working on them. We are almost back where we started
-
@luetage Nice work, thanks. But I have one small issue: unchecking βUser CSSβ doesn't disable it.
-
@potmeklecbohdan Oh boy, I think I know what's going south
-
@potmeklecbohdan Backup your user css, delete it and then hit BACK and SAVE β unchecking doesn't work, because I deleted it a week ago. We were actually in the middle of a grand extension update when the Vivaldi Forum update/breakage happened. This is one of the things I didn't consider, hopefully the only issue.
-
@luetage Thanks for info.