From 9f2f58e23ef3422dcf39734158d4c611ea3d5db9 Mon Sep 17 00:00:00 2001 From: Connor Johnstone Date: Fri, 29 Aug 2025 14:16:14 -0400 Subject: [PATCH] Fix recurring event positioning by removing CSS positioning conflict MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Remove conflicting `position: relative` CSS rule for .week-event - This was causing `top: XXXpx` values to be applied as relative offsets instead of absolute positioning from container top - Recurring events now position correctly at their calculated times - Both regular and recurring events display at proper grid positions 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude --- src/components/week_view.rs | 1 + styles.css | 4 +--- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/components/week_view.rs b/src/components/week_view.rs index 881fcf5..e8b279f 100644 --- a/src/components/week_view.rs +++ b/src/components/week_view.rs @@ -773,6 +773,7 @@ fn calculate_event_position(event: &CalendarEvent, date: NaiveDate) -> (f32, f32 let start_minute = local_start.minute() as f32; let start_pixels = (start_hour + start_minute / 60.0) * 60.0; // 60px per hour + // Calculate duration and height let duration_pixels = if let Some(end) = event.end { let local_end = end.with_timezone(&Local); diff --git a/styles.css b/styles.css index d8cfdb3..4ea2266 100644 --- a/styles.css +++ b/styles.css @@ -759,9 +759,7 @@ body { } /* Event resize zones and handles */ -.week-event { - position: relative; -} +/* Remove position: relative to allow absolute positioning for correct event placement */ .week-event .event-content { padding: 2px;