SMF 2.1 issues with new quickbuttons

[Akyhne]

In a post, hover over the More... button then try clicking on Modify, Remove or Split Topic. If you don\t exactly click the text, nothing happens.

[Antechinus]

Already fixed on local. Just a padding issue.

ETA: This is the current code for the quickbuttons droppy on my local.

Code Select Expand

.quickbuttons li ul {
position: absolute;
top: 1.9em;
left: -9999px;
z-index: 90;
padding: 0.5em;
font-weight: normal;
text-align: left;
background: #fff url(../images/theme/bars.png) 0 -580px repeat-x;
border: solid 1px #999;
border-left: solid 1px #aaa;
border-top: solid 1px #bbb;
border-radius: 4px 2px 4px 0;
box-shadow: 2px 3px 3px rgba(0,0,0,0.2);
}
.quickbuttons li:hover ul, .quickbuttons li.sfhover ul {
left: auto;
right: -1px;
}
.quickbuttons li.sfhover ul li, .quickbuttons li:hover ul li{
display: block;
background: none;
border: none;
box-shadow: none;
width: 12em;
border: 1px solid transparent;
border-radius: 3px;
}
.quickbuttons li ul li:hover {
border: 1px solid #cfcfcf;
border-top: 1px solid #d4dee6;
border-bottom: 1px solid #cbdae6;
background: #e3e9ef url(../images/theme/lower_section.png) 0 0 repeat-x;
}
.quickbuttons ul li a, .quickbuttons ul li a:focus {
padding: 0 6px 0 26px;
display: block;
line-height: 2.2em;
width: 12em;
-moz-box-sizing: border-box; -webkit-box-sizing: border-box; box-sizing: border-box;
}
/* Note: The next declarations are for keyboard access with js disabled. */
.quickbuttons ul li a:focus {
margin: 0 -9910px 0 9910px;
background: #e3e9ef url(../images/theme/lower_section.png) 0 0 repeat-x;
}
/* Cancel for hover and/or js access. */
.quickbuttons ul li:hover a:focus, .quickbuttons ul li.sfhover a:focus {
margin: 0;
}


[Akyhne]

Good! Thx.

[Antechinus]

There is still one buglet with those droppy links. At the moment they lose their icon on focus. I'll sort that too. Will probably use a pseudo for it to make things more bulletproof (IE8 etc).

[Antechinus]

Forgot something. There's a change to the markup for the "More.." button too. Reason is that the lack of a link there was borking keyboard access to teh droppy. IF there's a link in that button, keyboard access is fine. So, what I did was to follow the same principle that all the other drop menus follow: first link in the droppy is that same as the top level link.

Code Select Expand

// Can the user modify the contents of this post?
if ($message['can_modify'])
echo '
<li class="post_options"><a href="', $scripturl, '?action=post;msg=', $message['id'], ';topic=', $context['current_topic'], '.', $context['start'], '">', $txt['post_options'], '</a>';

echo '
<ul>';

[emanuele]

I don't remember if this is fixed, though a bump is good.

[Arantor]

This appears to be solved in 2.1.