Skip to content

fix: respect prompt_new_tab_name in mouse click handlers#521

Merged
ogulcancelik merged 2 commits into
ogulcancelik:masterfrom
imrajyavardhan12:master
Jun 9, 2026
Merged

fix: respect prompt_new_tab_name in mouse click handlers#521
ogulcancelik merged 2 commits into
ogulcancelik:masterfrom
imrajyavardhan12:master

Conversation

@imrajyavardhan12

Copy link
Copy Markdown
Contributor

Fixes #517

Summary

The desktop new-tab button and mobile switcher new-tab target were calling open_new_tab_dialog() unconditionally, ignoring the prompt_new_tab_name config setting. This caused the rename dialog to appear even when users had disabled it.

Changes

  • Added prompt_new_tab_name checks in both mouse click handlers (src/app/input/mouse.rs lines 440 and 1021)
  • When the config is false, the handlers now set request_new_tab = true and return to Mode::Terminal directly, matching the keyboard shortcut behavior in navigate.rs
  • Added two tests to verify both mouse paths skip the dialog when prompt_new_tab_name is false

Testing

All 1604 unit tests pass. The fix mirrors the existing keyboard path logic, so behavior is now consistent across input methods.

refs #517

The desktop new-tab button and mobile switcher new-tab target were
calling open_new_tab_dialog() unconditionally, ignoring the
prompt_new_tab_name config setting.

Added checks matching the keyboard path in navigate.rs to skip the
dialog when prompt_new_tab_name is false.

refs ogulcancelik#517
@kangal-bot

Copy link
Copy Markdown
Collaborator

Hi @imrajyavardhan12, thanks for your interest in contributing!

New contributors need maintainer approval before opening PRs. This keeps review time focused on accepted work and avoids wasted effort.

Herdr is opinionated about how it should look, feel, and work. Feature requests, ideas, questions, contribution proposals, and product-direction checks belong in Discussions, not issues.

Next steps:

  1. If this is a feature or behavior change, open a Discussion describing what you want to change and why
  2. If the work is accepted, a maintainer may convert the discussion into an issue or create a new issue for it
  3. If this is a reproducible bug, open a bug report using the issue template
  4. Wait for maintainer approval on an accepted issue before opening a PR
    Maintainers approve first-time PR paths with /approve @your-github-username on the accepted issue.
  5. Keep it concise and write in your own voice

A discussion, issue, branch, or proposed implementation does not reserve the work and does not mean the PR path is approved.

This PR will be closed automatically. See https://github.com/ogulcancelik/herdr/blob/master/CONTRIBUTING.md for more details.

@kangal-bot kangal-bot closed this Jun 9, 2026
@ogulcancelik ogulcancelik reopened this Jun 9, 2026
@ogulcancelik ogulcancelik merged commit 22fa503 into ogulcancelik:master Jun 9, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

new tab click ignores the config ui.prompt_new_tab_name = false

3 participants