Skip to content

Have item in popup box already selected for faster keyboard navigation #115

Open

Description

@shbach

There are certain popup boxes where if the item was already selected it would be more convenient for keyboard navigation.

Template selection popup

When selecting a template to insert, this pop up box shows:
Image

It would be helpful if the dropdown box was already highlighted:
Image

I could of course just press Tab but this saves me a keypress. Maybe this entire pop up box could be redesigned so it is more keyboard friendly but this would be a start.

Custom variables popup

If using custom variables in the template, this popup box shows up to input the value:
Image

Would be helpful if the text box is already highlighted like so:
Image

This way I can start typing without having to press Tab first.

Activity

  1. lukaslabryszewski commented on Nov 27, 2025

    @lukaslabryszewski

    I Agree. Previous implementation allowed me to press [F2] then use keyboard navigation so I could just type in first couple of letters of my template and press [Enter]. Unfortunately now this requires using a mouse.

    Thanks @shbach for the [Tab] suggestion. It's a good workaround for now.

    P.S. This is on Joplin 3.5.12 (prod, darwin) - macOS Sonoma (14.6.1)

  2. Aaravanand00 commented on Feb 20, 2026

    @Aaravanand00
    Contributor

    Hi @shbach,

    I reviewed and tested the current dialog behavior locally to verify the keyboard navigation concerns raised in this issue.

    After testing:

    • The template selection dropdown is automatically focused when the dialog opens.

    • The custom variable input field is also auto-focused.

    • Users can immediately type or use arrow keys without pressing Tab.

    • Enter and Escape behavior works as expected.

    I tested this by building the plugin locally and triggering both dialogs in development mode. No regressions or console errors were observed.

    From what I can see, the current implementation already satisfies the requested behavior.

    If there’s a specific environmen

  3. shbach commented on Feb 21, 2026

    @shbach
    Author

    Hi @shbach,

    I reviewed and tested the current dialog behavior locally to verify the keyboard navigation concerns raised in this issue.

    After testing:

    * The template selection dropdown is automatically focused when the dialog opens.
    
    * The custom variable input field is also auto-focused.
    
    * Users can immediately type or use arrow keys without pressing Tab.
    
    * Enter and Escape behavior works as expected.
    

    I tested this by building the plugin locally and triggering both dialogs in development mode. No regressions or console errors were observed.

    From what I can see, the current implementation already satisfies the requested behavior.

    If there’s a specific environmen

  4. shbach commented on Feb 21, 2026

    @shbach
    Author

    @Aaravanand00 I'm on Linux (GNOME). I've used both the appimage and the flatpak and I observe the behavior I described.

  5. Aaravanand00 commented on Feb 21, 2026

    @Aaravanand00
    Contributor

    Hi @shbach,

    Thank you for confirming that you're observing this behavior on Linux (GNOME). That helps narrow things down.

    On my local testing (different environment), both the template selection dropdown and the custom variable input field appear to receive focus automatically when the dialog opens.

    To better understand the discrepancy, could you please confirm:

    -  Your exact Joplin version
      
    -  Whether you're using Wayland or X11
      
    -  If this happens consistently every time the dialog opens
      
    -  Whether the dropdown appears focused visually but does not accept typing, or if it’s not focused at all
    

    If needed, I can add an explicit programmatic .focus() call after the dialog renders to ensure consistent behavior across platforms. Before preparing a PR, I’d just like to confirm the exact reproduction scenario to avoid introducing unnecessary changes.

    Looking forward to your feedback

  6. shbach commented on Feb 21, 2026

    @shbach
    Author

    @Aaravanand00

    1. Joplin 3.5.12
    2. Wayland
    3. Consistently
    4. Not focused at all
  7. Aaravanand00 commented on Feb 22, 2026

    @Aaravanand00
    Contributor

    Hi @shbach,

    Thank you for the detailed clarification — that helps a lot.

    Since this happens consistently on Joplin 3.5.12 under Wayland and the dropdown is not focused at all, it does look like a platform-specific focus issue rather than expected behavior.

    I’ll proceed with adding an explicit programmatic .focus() call after the dialog renders to ensure consistent focus behavior across environments (especially Wayland). The change will be minimal and limited to the dialog initialization logic.

    I’ll open a PR shortly for review.

    Thanks again for testing and confirming

  8. lukaslabryszewski commented on Feb 22, 2026

    @lukaslabryszewski

    Hi @Aaravanand00

    I observe the behavior @shbach described consistently, not focused until I press Tab.

    This is on Joplin 3.5.12 (prod, darwin) - macOS Sonoma (14.6.1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions