Vivaldi’s forum has been updated
-
I see the forum search can now match exactly the words you put in where previously it would search everything that had one of your search terms. This is much better now!
-
The unwanted menu is a constant irritation.
For example:
Close Tab:
Move Cursor to Unread:
-
@Pesala said in Vivaldi’s forum has been updated:
The unwanted menu is a constant irritation.
It's because of this:
#vivaldimenu .hov {padding-bottom: 15px;}
The code has 2 problems. First of all it makes overshooting easy, secondly it reduces the hit area of submenu items below it (eg recent doesn't trigger full height).Setting the padding-bottom to 0px solves both problems.
edit: it's not that easy it seems, as pointed out correctly by @sjudenim, the padding is needed to reach the menu. If there is no padding, the menu disappears… I guess that's something the Vivaldi devs are going to enjoy fixing -
@luetage said in Vivaldi’s forum has been updated:
If there is no padding, the menu disappears…
It does not if you set up this:
#vivaldimenu li.hov ul {top: 30px !important;}
But what difference does this:#vivaldimenu .hov {padding-bottom: 0px !important;}
really make? -
-
The positioning of the User Information when clicking on an icon in the reply to a post shows the wrong user's info, and is sometime a long way out of position. From this thread when clicking on Ayespy's icon in his reply to LonM.
Or click the icons of @gaelle and @pafflick above in their replies to luetage.
-
That's not really a fix either as it only serves to exacerbate the inconsistency of the menus.
Here you can see how the menus do not line up with one another (and I personally don't like the looks of them overlapping the header)
On top of that, I find the hover menus to not be intuitive because they do not have an active state while falling under 2 and sometimes 3 header buttons.
I've tried to address these issues in my theme with callouts
:before
the menu but this too is not perfect. The:before
section does overlap the navbar slightly to keep the menus open which will have false triggers for the navbar (hasn't really happened to me but the possibility is certainly there) -
@sjudenim Could a delay of 500 ms be set before the menus are opened? I think that would be long enough for moving the cursor over the tabs not to trigger them.
-
@sjudenim said in Vivaldi’s forum has been updated:
That's not really a fix either
But what are you trying to fix? I don't understand that. My solution was supposed to fix the only problem that I knew (from @luetage's post) which was the disappearing menu. Any other problems with the menus are unknown to me (besides the sub-menu overlapping the navigation bar, but it's not something that you can fix by adjusting padding by 15px), hence my initial question about the difference that this is supposed to make.
I'm still having a hard time trying to figure out what you're trying to achieve there, with that padding manipulation...@sjudenim said in Vivaldi’s forum has been updated:
Here you can see how the menus do not line up with one another
That is a problem on your side, I can't see that here (except for the notifications/chat/profile submenus, which are not lined up even with the original CSS - though the difference is smaller).
-
@Pesala said in Vivaldi’s forum has been updated:
@sjudenim Could a delay of 500 ms be set before the menus are opened? I think that would be long enough for moving the cursor over the tabs not to trigger them.
That's an idea. I'll look into trying to implement that.
-
@pafflick said in Vivaldi’s forum has been updated:
But what are you trying to fix? I don't understand that. My solution was supposed to fix the only problem that I knew (from @luetage's post) which was the disappearing menu. Any other problems with the menus are unknown to me (besides the sub-menu overlapping the navigation bar, but it's not something that you can fix by adjusting padding by 15px), hence my initial question about the difference that this is supposed to make.
I'm still having a hard time trying to figure out what you're trying to achieve there, with that padding manipulation...The default css has padding in it which caused false triggers. I assume @luetage's removal of it was to address that but doing so led to the disappearing menu.
@sjudenim said in Vivaldi’s forum has been updated:
Here you can see how the menus do not line up with one another
That is a problem on your side, I can't see that here (except for the notifications/chat/profile submenus, which are not lined up even with the original CSS - though the difference is smaller).
How is the problem just on my end if you acknowledge seeing the same thing? Your margin suggestion increases the inconsistency which is evident in the image I supplied.
The fact @gaelle is saying that the devs are looking for a fix would indicate that there is indeed an issue
-
Edit: still needs work
-
@sjudenim said in Vivaldi’s forum has been updated:
The default css has padding in it which caused false triggers. I assume @luetage's removal of it was to address that but doing so led to the disappearing menu.
I'm unable to reproduce any "false" triggers with the default CSS. The submenu opens only when the cursor is over the top (white) bar, and never while on the blue. The padding removal reduces the
:hover
area of the top buttons, but it's still quite easy to unintentionally overlay the navigation buttons with the submenus. That's why I was wondering what was this supposed to achieve because it doesn't really change anything.@sjudenim said in Vivaldi’s forum has been updated:
How is the problem just on my end if you acknowledge seeing the same thing?
I'm not seeing what you've shown on the screenshot, all of the submenus are aligned after removing the padding and adjusting the positioning:
The other submenus (on the right) are not consistent with the new submenus (on the left) in any way (different position, borders, corner rounding, hover effects, elements padding, etc., etc.), so I didn't even bother trying to align them.
-
I specifically said that the menus are inconsistent, I don't find disregarding some of them as a solution.
Adjusting the margins removes false triggers but there is still an element of the header that is overlapping the submenu. Notice how the hover on the submenu (second bar) is only responsive 3/4 of the way up to the header? Something makes it lose focus before it should.
Something like this works (though I had to reduce the header size slightly)
#vivaldiheader { margin-top: 0; height: 60px; } #vivaldiheader>.row { padding: 17px 20px; } #vivaldimenu a.has-submenu:hover { margin-top: -8px; padding-top: 13px; height: 60px; } #vivaldimenu .hov { padding-bottom: 0; height: 40px; } #vivaldimenu ul { border-top: 0; margin-top: 2px; } .dropdown-menu, #logged-in-menu .dropdown-menu { margin-top: -1px; } #submenu { top: 60px !important; height: 55px; } #submenu li, #submenu ul { height: 55px; line-height: 55px; } .dropdown-menu, #logged-in-menu .dropdown-menu { margin-top: -1px; }
-
@sjudenim said in Vivaldi’s forum has been updated:
there is still an element of the header that is overlapping the submenu
That's just the default style of the
ul
element (which has amargin-bottom
set to 10px). Easy fix:#vivaldimenu { margin-bottom: 0px; }
I've also tried your code, and to be honest, I couldn't see too much difference with the submenus behaviour. The
:hover
area is "cropped" at the bottom a little bit, so I guess that was the objective?
The submenus on the left seem to be 1px below the forum's submenus (easy to spot when you click the notification bell and then hover the "About" menu). -
Yes, besides the aesthetic aspect of having the menus on the same level (imo they should be styled the same too, one has a
border-radius
and nobox-shadow
while the other has the exact opposite), my fix is an attempt to address the dead space on the top of the#submenu
(you will notice it loses it's focus before you actually leave the button) as well as not having the header menu trigger before you leave the#submenu
.And for what its' worth, I think the header drop down menu could use this
#vivaldimenu ul li:first-of-type { border: 0 }
since there is a double line on top with the menu border
-
@sjudenim said in Vivaldi’s forum has been updated:
the dead space on the top of the #submenu
That's fixed with
#vivaldimenu { margin-bottom: 0; }
(try inspecting#vivaldimenu
with default CSS, you'll notice how it overlaps the#submenu
). Reducing themargin-bottom
to0
on#vivaldimenu
eliminates the "dead" space on the top of the#submenu
.@sjudenim said in Vivaldi’s forum has been updated:
not having the header menu trigger before you leave the #submenu
It's impossible to make it trigger without leaving the
#submenu
(with the default CSS at least). It's just a matter of accuracy. For that reason, the reducing of the:hover
area of the buttons should help those who move the cursor too far up, but the submenus continue to be an obstruction for those who move the cursor from above (like @Pesala has described above).The idea with the 500ms delay might actually be (a kind of) a solution, I've got something like this:
#vivaldimenu li.hov ul { display: block; visibility: hidden; transition: visibility 0s ease-out 0s; } #vivaldimenu li.hov:hover ul { visibility: visible; transition: visibility 0s ease-in 0.5s; }
-
@Pesala That's a bug indeed, thanks for mentioning it. Have you reported it already?
If so what's the number cause I couldn't find it in our bts.
If not, please do so, it's easier for us to follow it up internally then -> Link to bugreport
Thanks in advance -
@gaelle I haven't reported it on the bug-tracker.
-
@Quinca71 sorry for the trouble and thanks for sharing these issues. Would you please report them here so that we can follow them internally with the devs? Thanks a mil in advance