Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

(Bug report) Keyboard shortcuts in tree context menu are not in line with menu item #685

Closed
meichthys opened this issue Nov 27, 2024 · 4 comments
Assignees

Comments

@meichthys
Copy link
Contributor

Description

The keyboard shortcut seems to be a few pixels higher than the menu items in the tree context menu:
image

If i remove the padding-top formatting it seems to fix it:
image
image

TriliumNext Version

0.90.12

What operating system are you using?

Windows

What is your setup?

Local (no sync)

Operating System Version

Windows 11

Error logs

No response

@pano9000
Copy link
Member

pano9000 commented Jan 10, 2025

seems to be only present in the "legacy" styles, the new TriliumNext styles do not have this bug.
I'll submit a fix for these

edit: after looking at the CSS it seems to be also present in the new ones as well, but it's not as noticeable.

there is one comment in the styles.css file, that I need to do some research first though:

.dropdown-menu kbd {
float: right;
color: var(--muted-text-color);
border: none;
background-color: transparent;
box-shadow: none;
/* 0 padding needed otherwise this increases the size of dropdown after dynamic positioning (which is then screwed) */
padding-top: 0;
padding-bottom: 0;
}

will check this weekend :-)

@pano9000 pano9000 self-assigned this Jan 10, 2025
@eliandoran
Copy link
Contributor

@pano9000 , as long as the height of a single menu item does not increase after adjusting the padding you should be OK.

@pano9000
Copy link
Member

similar issue, slightly different exact cause
#976

I would propose switching to a Flexbox or Grid based layout for the context menu, instead of a "block" based one
@eliandoran would a change like that be OK, or would it be causing issues with existing Themes (especially third party ones)?
Not fully sure how the whole "theme" topic is realized here.

@eliandoran
Copy link
Contributor

@pano9000 , indeed flexbox seems to be a good way to go.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants