mirror of
https://github.com/Lidarr/Lidarr.git
synced 2026-03-03 00:26:58 -05:00
Pull Sonarr commit 'Fixed: Agenda view on mobile' #2622
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
Area: Update API
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Don't Merge
Status: Help Wanted
Status: In Progress
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
conflict
no-conflict
not-pulled
radarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Lidarr-Lidarr#2622
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @servarr[bot] on GitHub (Mar 27, 2023).
Pull
github.com/Sonarr/Sonarr@34e928ebedThis commit has 0 conflict(s)
You can ask me to
close all,open pr hereoropen pr everywhere@jasonpatrickellykrause commented on GitHub (Jan 1, 2026):
After investigation, this Sonarr commit is not applicable to Lidarr. The fix changes .event to .overlay in the CSS, but Lidarr's AgendaEvent component doesn't use an .overlay class - it only uses .event and .eventWrapper. This explains why PR #3453 was never merged. Recommend closing this issue as 'not applicable'.
@mynameisbogdan commented on GitHub (Jan 1, 2026):
Should be reopened.
My advice is to use the history or blame per file/folder in Sonarr to see what changed.
@jasonpatrickellykrause commented on GitHub (Jan 2, 2026):
Thanks for the review. I figured out at least part of what you were talking about.
github.com/Sonarr/Sonarr@8fff59ff10 (diff-e8c9a9c7ea)