@Quiddity thanks for raising this. Though we don't yet have standardized menu components we plan to in the future, so I'm trying to think both of general rules/standardized spacing here, as well as what's appropriate in this specific context. As a first step I think it would be easy to increase the padding around the menu divider element, which is something I see (for example) on the Github user menu:

github	updated Wikipedia

beyond that we get into sort of special-casing territory (which is perhaps appropriate here)... thoughts from a system perspective @Volker_E @bmartinezcalvo ?

@bmartinezcalvo @Sarai-WMDE Ha, funny coincidence. As much as I wasn't sure at the beginning of our conversation, this points more into the direction of having the divider a separate component.
@alexhollender_WMF We've been talking about header/footer treatment of menus. That or, when looking at the Github example with the other groups a grouping or a component way could all three point into the asked for direction. From a UX perspective I'm all in support for fulfilling your ask and tackle @Quiddity's shared problem.

In T300417#7665047, @Volker_E wrote:

@bmartinezcalvo @Sarai-WMDE Ha, funny coincidence. As much as I wasn't sure at the beginning of our conversation, this points more into the direction of having the divider a separate component.

@Volker_E @Sarai-WMDE yes, I think we should have the divider as separate component to prevent this and other problems.

In T300417#7664352, @alexhollender_WMF wrote:

As a first step I think it would be easy to increase the padding around the menu divider element, which is something I see (for example) on the Github user menu:

@alexhollender_WMF about the options we have to separate more the Logout from the previous item, I think adding more padding between items could be a good solution. What do you think if we add 4 px padding between all items (also adding 4px on top and on bottom of the dropdown menu) instead of adding padding only in Logout? With this solution we could also avoid clicking on other options that we don't want to click on (I think our menu options are currently too close).

In T300417#7667154, @bmartinezcalvo wrote:

What do you think if we add 4 px padding between all items (also adding 4px on top and on bottom of the dropdown menu) instead of adding padding only in Logout? With this solution we could also avoid clicking on >other options that we don't want to click on (I think our menu options are currently too close).

@bmartinezcalvo I think that extra space makes sense in this case. There are also other situations where we might want more compact spacing, for example a more basic menu:

then of course there are other needs of menus, such as section headings, etc. Which is really all to say: we should probably consider all menu needs when making decisions and designing the menu component.

There are also other situations where we might want more compact spacing, for example a more basic menu:

1. Too much spacing can also be frustrating in other instances!
I made this screenshot (F34939934) about 5 years ago to demonstrate my frustrations with the increased default OOUI menu size. But I understand that it can be helpful for mobile/tablet users (or those with accessibility challenges) to have larger click/tap-targets, so I don't think I ever linked it until now.

Well, it's not only mobile/tablet users, there's also an accessibility aspect to it for users with motor impairments and limitations. That and vast popularity of touch based interfaces both have influenced the 44 x 44 px success requirement.

@alexhollender_WMF We've actually put quite some thought into Menu sections design:

Related user-frustration thread at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Add_an_"are_you_sure?"_pop-up_when_you_log_out -- (permalink)