Core Tunnel 4.0.2: Local Port Forwarding fields cannot be focused by mouse click

[Arming4389]

Environment:

• Core Tunnel 4.0.2 (4712), Codinn Store / Direct version

• Bundle ID: io.coressh.tunnel-direct

• macOS 26.5 (25F71)

Issue:
In Edit Tunnel -> General -> Local Port Forwarding, the forwarding row fields look editable, but clicking them with the mouse does not focus the text fields. This makes Local Port Forwarding appear impossible to edit.

Steps to reproduce:

1. Open an existing tunnel that has Local Port Forwarding entries.

2. Choose Tunnel -> Edit Tunnel.

3. Go to General -> Local Port Forwarding.

4. Click the local port / target host / target port fields.

5. Try to edit the value.

Expected:
Clicking a Local Port Forwarding field should focus the clicked text field and allow editing.

Actual:
Mouse clicks do not focus the clicked field. Focus is taken by the parent table/outline instead, or sometimes jumps elsewhere. The fields themselves are still editable via keyboard navigation, so this appears to be a mouse focus / hit-testing issue rather than a data or permission issue.

Workaround:
Click the forwarding table, then press Tab to move into the fields. For the first row, Tab cycles through bind address, local port, target host, and target port.

Additional note:
For empty bind address values, the UI displays "bind_address" like visible text/placeholder. Combined with the mouse focus issue, this makes the row look even more like static, non-editable text.

Related:
This may be related to the earlier v4.0.1 report where Local Port Forwarding fields appeared not editable:
https://community.codinn.com/t/issues-with-core-tunnel-v4-0-1/4970

However, in this case the issue is specifically that mouse clicks do not focus the clicked text field, while keyboard Tab can still reach and edit the fields.

[Arming4389]

Update: I found the same workaround mentioned in the earlier v4.0.1 thread.

After selecting the forwarding row first, clicking the Host/Port field again, or pressing Enter, does allow editing.

So this is not that the forwarding fields are completely non-editable. The issue is that the fields visually look like directly editable text fields, but a normal click on the visible field does not focus or edit it. This makes the Local Port Forwarding table appear read-only or broken at first glance.

I think the issue is better described as an interaction / discoverability regression in the v4 UI: editing is technically possible, but the required row-select + second-click / Enter workflow is easy to miss.

It would be helpful if clicking directly on a visible Host/Port field could enter edit mode, or if the UI made the required edit mode more obvious.

[yang (Yang.Y)]

@Arming4389

It would be helpful if clicking directly on a visible Host/Port field could enter edit mode, or if the UI made the required edit mode more obvious.

This is the default behavior of native macOS applications. For example, in Finder's Settings… > Tags, if you want to rename a tag, you need to click the row twice before entering edit mode: the first click selects the row, and the second click (or pressing Return) starts editing. I tend to prefer keeping the behavior consistent with the system.