[WEB-6610] Fix work item drag handle hover gap

[iam-vipin]

Summary

• extend the work item description editor hover area to the left
• keep the description text visually aligned while bringing the drag handle inside the editor container

Video

Screen.Recording.2026-03-13.at.4.50.57.PM.mov

Testing

• confirmed the drag handle stays visible when moving the cursor slowly from the editor content toward the handle

Summary by CodeRabbit

• Style
  • Adjusted the spacing and alignment of the description input component for improved visual presentation.

[makeplane]

Linked to Plane Work Item(s)

• [WEB-6610] drag handle dont stay visible when moving the cursor slowly from the editor content toward the handler

This comment was auto-generated by Plane

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 719875a6-73b3-414b-b11f-834caa50e850

📥 Commits

Reviewing files that changed from the base of the PR and between 6627282 and 49a17e0.

📒 Files selected for processing (1)

• apps/web/core/components/issues/issue-detail/main-content.tsx

---

📝 Walkthrough

Walkthrough

A styling adjustment to the DescriptionInput container in the issue detail view, modifying margin and padding classes to refine visual layout. The change introduces negative left margin and adjusted left padding while maintaining other style properties.

Changes

Cohort / File(s)	Summary
Layout Styling Update apps/web/core/components/issues/issue-detail/main-content.tsx	Updated DescriptionInput container classes from p-0 border-none to -ml-6 border-none p-0! pl-6!, adjusting left margin and left padding for layout refinement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A margin tweak, a padding fix,
With -ml-6 and pl-6 mix,
The layout dances left and right,
Our UI's dressed in pixel light! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes a summary of changes, a demonstration video, and testing confirmation, but lacks the structured template sections (Type of Change, Screenshots/Media, Test Scenarios, References).	Consider using the repository's description template to organize information into Type of Change, Screenshots/Media, Test Scenarios, and References sections for consistency.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately references the specific issue (WEB-6610) and describes the main fix: resolving a hover gap with the work item drag handle.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/fix-workitem-drag-handle-hover

📝 Coding Plan

• Generate coding plan for human review comments

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can approve the review once all CodeRabbit's comments are resolved.

Enable the reviews.request_changes_workflow setting to automatically approve the review once all CodeRabbit's comments are resolved.