feat(css-map): add track list disabled class

[D3SOX]

As I messaged on Discord the "More Visible Unplayable Tracks" snippet has been broken and I think this is the correct solution for this problem

[coderabbitai]

Walkthrough

This pull request adds a single CSS class mapping entry to css-map.json, mapping the identifier "Unhd72dSzMriFEuvX2UU" to the class name "main-trackList-disabled" for player UI styling.

Changes

Cohort / File(s)	Summary
CSS Mapping Addition css-map.json	Added one new mapping entry: "Unhd72dSzMriFEuvX2UU" → "main-trackList-disabled"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

• Verify that the mapping identifier "Unhd72dSzMriFEuvX2UU" is correct and corresponds to the intended UI element
• Confirm the class name "main-trackList-disabled" follows the existing naming convention in the file

Possibly related PRs

• feat(css-map): add player classes for 1.2.73 #3529: Adds multiple player UI class mappings to css-map.json, including similar CSS identifier-to-class-name mappings for player-related elements

Suggested reviewers

• rxri
• kyrie25

Poem

🐰 A hop and a skip through the CSS terrain,
A mapping so simple, no code to refrain,
Unhd72dSzMriFEuvX2UU finds its way,
To main-trackList-disabled, hip-hip-hooray! 🎵

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The pull request title 'feat(css-map): add track list disabled class' directly and clearly summarizes the main change: adding a new CSS mapping entry for a track list disabled class.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}