Skip to content

ui: Fix headless track selection bug#2811

Merged
stevegolton merged 1 commit intomainfrom
dev/sg/fix-headless-track-selection-bug
Sep 3, 2025
Merged

ui: Fix headless track selection bug#2811
stevegolton merged 1 commit intomainfrom
dev/sg/fix-headless-track-selection-bug

Conversation

@stevegolton
Copy link
Member

When selecting over a headless track (users are unaware of this because headless tracks are invisible), the entire group is selected as this is the behavior when selecting over a non-headless track.

This patch fixes the issue by omitting headless tracks from the rendered track list so the selection logic never even sees them.

Fixes: https://buganizer.corp.google.com/issues/442408089

headless track.

Change-Id: I270f57f8666d2931887f34fc27f498dd6666402c
@stevegolton stevegolton requested a review from a team as a code owner September 3, 2025 08:25
@github-actions
Copy link

github-actions bot commented Sep 3, 2025

🤖 Hi @stevegolton, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📋 Review Summary

This pull request refactors the track rendering logic to correctly handle headless tracks, preventing them from being selectable. The changes are clear, concise, and improve the maintainability of the code.

🔍 General Feedback

  • The logic for handling headless tracks is now much cleaner and easier to understand.
  • The change to an IIFE for isTrackOnScreen is a minor stylistic improvement.

@stevegolton stevegolton merged commit 56fd4c5 into main Sep 3, 2025
33 checks passed
@stevegolton stevegolton deleted the dev/sg/fix-headless-track-selection-bug branch September 3, 2025 12:31
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.

3 participants