Unified search placeholders shouldn't use dynamic svg gradients
Open
Nobody has claimed this yet.
1. to develop
feature: search
performance 🚀
technical debt
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
@PVince81 mentioned in https://github.com/nextcloud/deck/pull/2934#discussion_r611532836 that svg gradients have quite some performance impact as they are not GPU accelerated.
The globa search resuls UI in deck currently still used them so we should have a look at https://github.com/nextcloud/spreed/pull/4554#issue-516786063 for an alternative implementation.
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 the global search results UI in the Deck frontend and compare its SVG gradient usage with the alternative implementation described in nextcloud/spreed#4554. Confirm which dynamic gradients remain, then verify that the search placeholders keep their appearance without using them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, search
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100