OpenCut-app / OpenCut-app/OpenCut
[BUG] Non-functional Eye Button on Timeline Track
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.8k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
Platform
Windows 11
Browser
Chrome 137
Current Behavior
The eye icon button on timeline track labels (left sidebar) is currently non-functional. It is displayed but does not respond to clicks, making it impossible to toggle track visibility.
Eye icon is visible on track labels
Clicking the icon triggers no action
No visual feedback (hover/active states)
Track content remains visible regardless of interaction
Expected Behavior
Clicking the eye icon should toggle track visibility
Visible State: Icon is a gray Eye
Hidden State: Icon becomes a red EyeOff
and track content becomes semi-transparent
Hidden tracks should not be included in the final export (if applicable)
Recurrence Probability
Always
Steps To Reproduce
- Open a project in the editor
- Add any media (video/image/text) to the timeline
- Locate the track label on the left sidebar
- Click the eye icon
- Observe that nothing happens
Anything else?
This PR implements the missing functionality for the timeline track visibility toggle. It allows users to hide/show specific tracks, which is essential for complex editing workflows
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start at the timeline track labels in the editor's left sidebar and reproduce the click from the issue's steps. Trace the eye button's state and track rendering, then verify that visible tracks show Eye, hidden tracks show EyeOff with semi-transparent content, and hidden tracks are excluded from export when applicable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100