Skip to content

Conversation

marcelytumy
Copy link

@marcelytumy marcelytumy commented Aug 17, 2025

…t looks less silly

Description

The previous upload button was visually heavy and inconsistent with the rest of the media panel controls, making the toolbar look unbalanced and silly.

Type of change

  • New feature (non-breaking change which adds functionality)
  • Code refactoring

Screenshots

before
image

after
image

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have added screenshots if ui has been changed
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Summary by CodeRabbit

  • New Features

    • Added a tooltip to the upload button displaying “Upload media” on hover.
  • Style

    • Replaced the large outlined upload button with a compact icon button while keeping the same upload flow.
    • Updated the upload icon and refined loading spinner styling for a cleaner look.
    • The button now shows a spinner during processing and the upload icon otherwise.
  • Refactor

    • Streamlined upload control visuals without altering file selection or drag-and-drop behavior.

Copy link

vercel bot commented Aug 17, 2025

@marcelytumy is attempting to deploy a commit to the OpenCut OSS Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

netlify bot commented Aug 17, 2025

👷 Deploy request for appcut pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit 73fdd0d

Copy link
Contributor

coderabbitai bot commented Aug 17, 2025

Walkthrough

Replaced the upload control’s icon and button style, added a tooltip, and adjusted spinner sizing within the media panel view. The underlying file selection, processing, and drag-and-drop logic remain unchanged.

Changes

Cohort / File(s) Summary of changes
Media Panel Upload UI
apps/web/src/components/editor/media-panel/views/media.tsx
Switched CloudUpload to lucide-react Upload icon; replaced outline lg button with compact text/icon button; wrapped button in Tooltip ("Upload media"); updated spinner to Loader2 with !size-4; conditional icon/spinner preserved; no logic changes to file handling.

Sequence Diagram(s)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I tapped the sky with a lighter touch, click-click—upload I must!
A tiny spin, a twirl so thin, while files rise free of dust.
Tooltips whisper, “Up you go,” in tidy, gleaming code—
Small buttons, big ambitions—hare-speed on the road!
Hop, upload, done—carrot-approved payload! 🥕🚀

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
apps/web/src/components/editor/media-panel/views/media.tsx (1)

297-315: Tooltips on disabled buttons may not show; consider wrapper pattern

Many tooltip libs (e.g., Radix-based) don’t show tooltips on disabled elements. If you want the tooltip to remain visible while isProcessing is true, wrap the disabled button with a non-disabled element and use it as the trigger.

Here’s the pattern using a span wrapper (can be combined with the previous diff):

-                <Tooltip>
-                  <TooltipTrigger asChild>
-                    <Button
+                <Tooltip>
+                  <TooltipTrigger asChild>
+                    <span className="inline-flex" aria-disabled={isProcessing}>
+                      <Button
                         variant="text"
                         size="icon"
                         type="button"
                         aria-label={isProcessing ? "Uploading…" : "Upload media"}
                         onClick={handleFileSelect}
                         disabled={isProcessing}
-                    >
+                      >
                         {isProcessing ? (
                           ...
                         ) : (
                           ...
                         )}
-                    </Button>
+                      </Button>
+                    </span>
                   </TooltipTrigger>
                   <TooltipContent>
                     <p>Upload media</p>
                   </TooltipContent>
                 </Tooltip>
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 13dff38 and 73fdd0d.

📒 Files selected for processing (1)
  • apps/web/src/components/editor/media-panel/views/media.tsx (2 hunks)
🧰 Additional context used
📓 Path-based instructions (5)
**/*.{jsx,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{jsx,tsx}: Don't use accessKey attribute on any HTML element.
Don't set aria-hidden="true" on focusable elements.
Don't add ARIA roles, states, and properties to elements that don't support them.
Don't use distracting elements like <marquee> or <blink>.
Only use the scope prop on <th> elements.
Don't assign non-interactive ARIA roles to interactive HTML elements.
Make sure label elements have text content and are associated with an input.
Don't assign interactive ARIA roles to non-interactive HTML elements.
Don't assign tabIndex to non-interactive HTML elements.
Don't use positive integers for tabIndex property.
Don't include "image", "picture", or "photo" in img alt prop.
Don't use explicit role property that's the same as the implicit/default role.
Make static elements with click handlers use a valid role attribute.
Always include a title element for SVG elements.
Give all elements requiring alt text meaningful information for screen readers.
Make sure anchors have content that's accessible to screen readers.
Assign tabIndex to non-interactive HTML elements with aria-activedescendant.
Include all required ARIA attributes for elements with ARIA roles.
Make sure ARIA properties are valid for the element's supported roles.
Always include a type attribute for button elements.
Make elements with interactive roles and handlers focusable.
Give heading elements content that's accessible to screen readers (not hidden with aria-hidden).
Always include a lang attribute on the html element.
Always include a title attribute for iframe elements.
Accompany onClick with at least one of: onKeyUp, onKeyDown, or onKeyPress.
Accompany onMouseOver/onMouseOut with onFocus/onBlur.
Include caption tracks for audio and video elements.
Use semantic elements instead of role attributes in JSX.
Make sure all anchors are valid and navigable.
Ensure all ARIA properties (aria-*) are valid.
Use valid, non-abstract ARIA roles for elements with...

Files:

  • apps/web/src/components/editor/media-panel/views/media.tsx
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{ts,tsx}: Don't use TypeScript enums.
Don't export imported variables.
Don't add type annotations to variables, parameters, and class properties that are initialized with literal expressions.
Don't use TypeScript namespaces.
Don't use non-null assertions with the ! postfix operator.
Don't use parameter properties in class constructors.
Don't use user-defined types.
Use as const instead of literal types and type annotations.
Use either T[] or Array<T> consistently.
Initialize each enum member value explicitly.
Use export type for types.
Use import type for types.
Make sure all enum members are literal values.
Don't use TypeScript const enum.
Don't declare empty interfaces.
Don't let variables evolve into any type through reassignments.
Don't use the any type.
Don't misuse the non-null assertion operator (!) in TypeScript files.
Don't use implicit any type on variable declarations.
Don't merge interfaces and classes unsafely.
Don't use overload signatures that aren't next to each other.
Use the namespace keyword instead of the module keyword to declare TypeScript namespaces.
Don't use empty type parameters in type aliases and interfaces.
Don't use any or unknown as type constraints.
Don't use the TypeScript directive @ts-ignore.
Use consistent accessibility modifiers on class properties and methods.
Use function types instead of object types with call signatures.
Don't use void type outside of generic or return types.

**/*.{ts,tsx}: Don't use primitive type aliases or misleading types
Don't use the TypeScript directive @ts-ignore
Don't use TypeScript enums
Use either T[] or Array consistently
Don't use the any type

Files:

  • apps/web/src/components/editor/media-panel/views/media.tsx
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit Inference Engine (.github/copilot-instructions.md)

**/*.{js,jsx,ts,tsx}: Don't use the return value of React.render.
Don't use consecutive spaces in regular expression literals.
Don't use the arguments object.
Don't use primitive type aliases or misleading types.
Don't use the comma operator.
Don't write functions that exceed a given Cognitive Complexity score.
Don't use unnecessary boolean casts.
Don't use unnecessary callbacks with flatMap.
Use for...of statements instead of Array.forEach.
Don't create classes that only have static members (like a static namespace).
Don't use this and super in static contexts.
Don't use unnecessary catch clauses.
Don't use unnecessary constructors.
Don't use unnecessary continue statements.
Don't export empty modules that don't change anything.
Don't use unnecessary escape sequences in regular expression literals.
Don't use unnecessary labels.
Don't use unnecessary nested block statements.
Don't rename imports, exports, and destructured assignments to the same name.
Don't use unnecessary string or template literal concatenation.
Don't use String.raw in template literals when there are no escape sequences.
Don't use useless case statements in switch statements.
Don't use ternary operators when simpler alternatives exist.
Don't use useless this aliasing.
Don't initialize variables to undefined.
Don't use the void operators (they're not familiar).
Use arrow functions instead of function expressions.
Use Date.now() to get milliseconds since the Unix Epoch.
Use .flatMap() instead of map().flat() when possible.
Use literal property access instead of computed property access.
Don't use parseInt() or Number.parseInt() when binary, octal, or hexadecimal literals work.
Use concise optional chaining instead of chained logical expressions.
Use regular expression literals instead of the RegExp constructor when possible.
Don't use number literal object member names that aren't base 10 or use underscore separators.
Remove redundant terms from logical expressions.
Use while loops instead of...

Files:

  • apps/web/src/components/editor/media-panel/views/media.tsx
**/*.{tsx,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/ultracite.mdc)

**/*.{tsx,jsx}: Always include a title element for icons unless there's text beside the icon
Always include a type attribute for button elements
Accompany onClick with at least one of: onKeyUp, onKeyDown, or onKeyPress
Accompany onMouseOver/onMouseOut with onFocus/onBlur
Don't import React itself
Don't define React components inside other components
Don't use both children and dangerouslySetInnerHTML on the same element
Don't insert comments as text nodes
Use <>...</> instead of ...

Files:

  • apps/web/src/components/editor/media-panel/views/media.tsx
**/*.{ts,tsx,js,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/ultracite.mdc)

**/*.{ts,tsx,js,jsx}: Don't use the comma operator
Use for...of statements instead of Array.forEach
Don't initialize variables to undefined
Use .flatMap() instead of map().flat() when possible
Don't assign a value to itself
Avoid unused imports and variables
Don't use await inside loops
Don't hardcode sensitive data like API keys and tokens
Don't use the delete operator
Don't use global eval()
Use String.slice() instead of String.substr() and String.substring()
Don't use else blocks when the if block breaks early
Put default function parameters and optional function parameters last
Use new when throwing an error
Use String.trimStart() and String.trimEnd() over String.trimLeft() and String.trimRight()

Files:

  • apps/web/src/components/editor/media-panel/views/media.tsx
🧬 Code Graph Analysis (1)
apps/web/src/components/editor/media-panel/views/media.tsx (2)
apps/web/src/components/ui/tooltip.tsx (3)
  • Tooltip (72-72)
  • TooltipTrigger (72-72)
  • TooltipContent (72-72)
apps/web/src/components/ui/button.tsx (1)
  • Button (61-61)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Vade Review
🔇 Additional comments (1)
apps/web/src/components/editor/media-panel/views/media.tsx (1)

8-8: Icon swap to lucide-react Upload looks good

Replacing CloudUpload with Upload aligns with the rest of the lucide icon set usage and supports the new compact control.

Comment on lines +299 to +311
<Button
variant="text"
size="icon"
onClick={handleFileSelect}
disabled={isProcessing}
>
{isProcessing ? (
<Loader2 className="!size-4 animate-spin" />
) : (
<Upload className="!size-4" />
)}
</Button>
</TooltipTrigger>
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Add button type and accessible name; include titles on icons

  • Buttons must declare type to avoid unintended form submissions.
  • Icon-only buttons need an accessible name; tooltips do not provide an accessible name for assistive tech.
  • Our guidelines require a title element for SVG icons in TSX/JSX.

Apply the following changes:

  • Add type="button" and a descriptive aria-label to the Button.
  • Add title to both icons (and optionally aria-hidden to avoid double announcements).
  • Optionally normalize icon stroke width to match adjacent controls and reduce visual weight.
-                    <Button
-                      variant="text"
-                      size="icon"
-                      onClick={handleFileSelect}
-                      disabled={isProcessing}
-                    >
-                      {isProcessing ? (
-                        <Loader2 className="!size-4 animate-spin" />
-                      ) : (
-                        <Upload className="!size-4" />
-                      )}
+                    <Button
+                      variant="text"
+                      size="icon"
+                      type="button"
+                      aria-label={isProcessing ? "Uploading…" : "Upload media"}
+                      onClick={handleFileSelect}
+                      disabled={isProcessing}
+                    >
+                      {isProcessing ? (
+                        <Loader2
+                          className="!size-4 animate-spin"
+                          strokeWidth={1.5}
+                          aria-hidden="true"
+                          title="Uploading…"
+                        />
+                      ) : (
+                        <Upload
+                          className="!size-4"
+                          strokeWidth={1.5}
+                          aria-hidden="true"
+                          title="Upload media"
+                        />
+                      )}
                     </Button>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<Button
variant="text"
size="icon"
onClick={handleFileSelect}
disabled={isProcessing}
>
{isProcessing ? (
<Loader2 className="!size-4 animate-spin" />
) : (
<Upload className="!size-4" />
)}
</Button>
</TooltipTrigger>
<Button
variant="text"
size="icon"
type="button"
aria-label={isProcessing ? "Uploading…" : "Upload media"}
onClick={handleFileSelect}
disabled={isProcessing}
>
{isProcessing ? (
<Loader2
className="!size-4 animate-spin"
strokeWidth={1.5}
aria-hidden="true"
title="Uploading…"
/>
) : (
<Upload
className="!size-4"
strokeWidth={1.5}
aria-hidden="true"
title="Upload media"
/>
)}
</Button>
🤖 Prompt for AI Agents
In apps/web/src/components/editor/media-panel/views/media.tsx around lines 299
to 311, the icon-only Button is missing a button type and accessible name and
the SVG icons lack title attributes; update the Button to include type="button"
and a descriptive aria-label (e.g., aria-label="Upload media" or similar), add a
<title> to each SVG icon (and set aria-hidden="true" on the SVGs if you want to
avoid duplicate announcements), and optionally normalize the icons' strokeWidth
to match adjacent controls for consistent visual weight.

<TooltipContent>
<p>Upload media</p>
</TooltipContent>
</Tooltip>
Copy link

Choose a reason for hiding this comment

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

Missing closing </Tooltip> tag after the view mode button's TooltipContent, causing invalid JSX structure when the next <Tooltip> opens.

View Details
📝 Patch Details
diff --git a/apps/web/src/components/editor/media-panel/views/media.tsx b/apps/web/src/components/editor/media-panel/views/media.tsx
index ec85507..abca8b1 100644
--- a/apps/web/src/components/editor/media-panel/views/media.tsx
+++ b/apps/web/src/components/editor/media-panel/views/media.tsx
@@ -343,7 +343,8 @@ export function MediaView() {
                         : "Switch to grid view"}
                     </p>
                   </TooltipContent>
-                  <Tooltip>
+                </Tooltip>
+                <Tooltip>
                     <DropdownMenu>
                       <TooltipTrigger asChild>
                         <DropdownMenuTrigger asChild>

Analysis

The tooltip structure for the view mode button (starting at line 316) is not properly closed before a new tooltip opens at line 346. The current structure has:

  1. <Tooltip> opens at line 316 (view mode button)
  2. </TooltipContent> closes at line 345
  3. <Tooltip> opens again at line 346 (dropdown button)

However, there's no </Tooltip> tag to close the view mode button's tooltip before the dropdown tooltip starts. This creates invalid JSX structure where tooltips are improperly nested, which will cause React rendering errors or compilation failures.

The structure should be:

</TooltipContent>
</Tooltip>  // ← This is missing
<Tooltip>

Recommendation

Add the missing </Tooltip> closing tag after line 345 (</TooltipContent>) and before line 346 (<Tooltip>). The corrected structure should be:

</TooltipContent>
</Tooltip>
<Tooltip>

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.

1 participant