Vivaldi’s forum has been updated
-
@luetage Whilst i can see why you might have interpreted my post as alleging that i said the update changed these font sizes, a careful re-reading of my words reveals i said no such thing. The reality is slightly more indirect:
- For more than a year, maybe even two years now, my view of the forum has been filtered through my [original] Stylus css.
- Said css reduced the target font size, hence, i "never" saw these current big fonts.
- Per a previous-but-recent post of mine associated with the new forum update, my Stylus css was broken by the update, or if you prefer, my original css broke the new forum [MGs & AutoScroll broke].
- Hence i had to switch off my original Stylus for the V forum, & "instantly" i was confronted with now-huge fonts where i indicated.
- My new Stylus css for the forum is successful wrt all colours i want, & some other tweaks, & of course fully-functional wrt MGs & AS, but naturally now still has the huge fonts... til i learn how to shrink them.
- None of the ways i've tried has worked, hence my plea for help.
What i used to see:
What i now see:
-
@Quinca71 said in Vivaldi’s forum has been updated:
nothing to do with the settings of Vivaldi > Navigation (or Browsing - my Viv is into PTBr) > minimum size of fonts
No. I have not changed this for a long time:
See the "g" of the word "switching"
Extremely well spotted; bravo. I'd missed that. In my new Stylus css i explicitly change the font to Lato:
/* Change forum font style */ html, body { font-family: "Lato" !important }
However when i then searched my original css [https://forum.vivaldi.net/post/255803] for its font-family, none was set, hence i presume it simply allowed inheritance of the native Vivaldi forum page design[?]. Btw, whereas i wrote the new css [+ borrowing some sections from clever people's code pasted in this thread & another], my original one was a pastiche from an older Sprucy design, with my colour changes added; it is considerably more complex than my own new one.
UPDATE: Yay, i stumbled across the magic; successfully added the following to my new css & it solves the problem:
/* Steffie 2/12/18: This DOES scale V's forum "Unread" & "Recent" page fonts; i nicked the following lines... */ .topic-title, a { color: #2c5e94; /* font-size: 15px !important; */ font-size: 88%; } span.timeago { color: #b05158 !important; } .stats { font-size: 14px !important; text-align: center; margin-top: 7px; line-height: 22px; } .dropdown-menu { font-size: 11px; } .avatar.avatar-md { width: 28px; height: 28px; line-height: 28px; } /* ...from my original V Stylus css, which in turn came from me adapting the original Vivaldi Sprucy theme. */
Thanks, @Quinca71 , it was your keen eagle-eyes that lead me to this discovery
-
This post is deleted! -
@gaelle said:
You can now see all your uploads by visiting https://forum.vivaldi.net/me/uploads
It looks like clicking the trash icon doesn't delete it. Is it there only for hiding it from the list or is it a bug?
-
@Quinca71 Yes, it is an unpolished feature and difficult to use until you know how.
- Type the username or part of it in the search box
- Select the username from the drop list
- Toggle the Blocked user
- Repeat the process to unblock the user later.
-
@Quinca71 Blocking a user hides all posts that they have made, and all threads that they have started.
-
I notice that there is now a min width for the chat page. this makes it difficult to use in a narrow panel as the right half of the messages get cut off:
-
Seems like we finally got voting indicators in default Vivaldi .
-
@luetage Yeah, I noticed too. But the use of the famous, indispensable
!important
directive broke my custom CSS - I don't like the blue, so I have to find a new workaround... -
@pafflick Haven't looked at it yet, but shouldn't be too hard. I'll let you know when I come around fixing this for vfm.
-
-
@pafflick Hmm, there is nothing we can do about it. The css style is overwritten by javascript, that means no css we run can change that. I think it would be possible to introduce an extra class with javascript and override it this way, but that's silly.
edit: I have issued a bug report for this.
-
@luetage said in Vivaldi’s forum has been updated:
@pafflick Hmm, there is nothing we can do about it.
Challenge accepted!!!
Well, actually I'm a bit of disappointed - first because you give up so easily and second because it was actually quite easy - it took me only 1 (one) try and it seems to work well with my code (I already used the golden
!important
rule before). The only reason I didn't check that earlier is that I had to take my mom's cat to the vet and I had to leave the house shortly after posting the previous comment....topic .votes [component="post/upvote"].upvoted { background-color: color-here !important; } .topic .votes [component="post/downvote"].downvoted { background-color: color-here !important; }
//EDIT: If you're wondering why this works or how to overrule
!important
directives, you should learn more about rules priority/precedence in CSS (or just keep them in mind if you're already familiar with them) -
@Quinca71 Thanks, you made me smile with the "cat's mother". It was my mother's cat, not the cat's mother...
-
@pafflick That works. Will be useful. And yeah, you are an amazing talent and everything comes easy to you . I'm very sorry that I disappointed you
and I hope it won't happen again :P. Thank you for your kind words, I will make sure to look deeper into the convoluted world of css trickery. Additionally I won't give up so fast again. Gladly the Vivaldi community is wholesome and helpful and therefore everyone helps each other out as best as they can -
@pafflick said in Vivaldi’s forum has been updated:
.topic .votes [component="post/upvote"].upvoted {
background-color: color-here !important;
}
.topic .votes [component="post/dwonvote"].downvoted {
background-color: color-here !important;
}One thing to note though, for people who happen to copy/paste this code. You wrote
dwonvote
isntead ofdownvote
, which will not work Maybe you should try to be more careful when posting code to make the experience more hassle-free -
@luetage Good catch, I used the correct code in my custom CSS, but then I manually edited the one that I copied from my old custom CSS - that's where I made the typo. Well, I mean - I shouldn't do everything by myself, shouldn't I? I've got to leave some work for others as well, right?
-
@pafflick This is correct! You are already doing so much for the community, it's only fair that the rest of us lends a hand from time to time, and be it just to correct a typo. I'm so glad I could help out, cheers!
-
I noticed, since the update, that I frequently open the Features menu when I go to click the Recent threads link.
What changed that causes this problem?
-
@pafflick OMZ, your genius shines thru' once again! Thanks.
Spoiler