[BUG] Meeting transcript: "Reassign to" and "Merge into" submenus close before they can be used (mouse and keyboard)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start by locating the transcript segment context menu and speaker chip menu, then inspect how their “Reassign to” and “Merge into” submenus handle pointer and keyboard navigation. Reproduce both cases in a finished meeting with at least two speakers. Done means each submenu stays open, lists eligible speakers, and lets a speaker be selected to reassign or merge.
Written by the indexing model from the issue text.
Description
Describe the bug
In a finished meeting transcript, two submenus close before I can use them:
- "Reassign to" in the context menu of a transcript segment (right-click a segment).
- "Merge into" in the menu of a speaker chip.
The submenu disappears before the pointer reaches it, so no target speaker can be chosen. Navigating with the keyboard instead (arrow keys) doesn't work either. As a result, I can't reassign a segment or merge speakers from the transcript.
Reproduction steps
- Open a finished meeting that has at least two speakers.
- Right-click a transcript segment and move the pointer to "Reassign to", then try to enter the submenu with the mouse or open it with the arrow keys.
- Open the menu of a speaker chip and move the pointer to "Merge into", then try the same.
Expected behavior
Each submenu stays open and lists the eligible speakers. Choosing one reassigns the segment or merges the speaker.
Actual behavior
Both submenus disappear before they can be entered. Keyboard navigation doesn't open them either. No speaker can be chosen.
App Version
1.6.11 (build 28)
macOS Version
26.6.2
Architecture
Apple Silicon (arm64)
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 863
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 28
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from altic-dev/FluidVoice
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
altic-dev/FluidVoice#1191 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
altic-dev/FluidVoice#1175 · 1 comment ·
Maintainers usually reply within 1 day
-
[BUG] File transcription skips audio chunks shorter than one secondPossibly taken @sabbah13 claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
altic-dev/FluidVoice#1161 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
altic-dev/FluidVoice#1202 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
altic-dev/FluidVoice#1201 ·
Maintainers usually reply within 1 day
All issues in altic-dev/FluidVoice
Similar issues
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
marcovisona/arca#5 ·
-
accessibility bug medium-priority mobile
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
lognorman20/monaco#6247 ·
-
documentation windows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
swiftlang/swift-format#1312 ·