separate spicetify menu items from spotify ones
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 24.6k
- Forks
- 941
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 24
Description
📝 Provide a description of the new feature
for example:
- check through list of all li items
- pick out the one containing an svg with aria-label External link
- append
vvMORUKtQKpQcpQ992bRclassname to its button
alternatively:
or via some other method idk how menu items and context menus now work, potentially create a store of all menu items registered like we do with topbar buttons and if its the first one to be registered add a border to the bottom of it instead? that approach could also work for normal context menus that way!
➕ Additional Information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating how Spotify menu items and context menus are registered, then compare that with the existing topbar button registration approach mentioned in the issue. The issue suggests either identifying the item containing an SVG with aria-label "External link" and adding the vvMORUKtQKpQcpQ992bR class, or separating registered menu items with a bottom border. Done means Spicetify and Spotify menu items are visually distinct without breaking normal context menus.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100