Fix recurring event positioning by removing CSS positioning conflict
- 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 <noreply@anthropic.com>
This commit is contained in:
@@ -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);
|
||||
|
||||
@@ -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;
|
||||
|
||||
Reference in New Issue
Block a user