MarleaM / MarleaM/OffBeets

Animations do not work on certain displays

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CSS Frontend good first issue
Dominant language
Python
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Our current animations (sliding fade-in) work on a majority of displays, but on a select few, they do not load.

Gets Called By: SongRows.tsx
File location: Anti-Spotify/frontend/src/App.css
Code location: Lines 375. Sample is pasted below.
```
/* animation */

@keyframes song-fade-in-animation {
0% {
opacity: 0;
transform: translateY(30px) scale(0.9);
}
100% {
opacity: 1;
transform: translateY(0px) scale(1);
}
}

@keyframes navbar-fade-down-animation {
0% {
opacity: 0;
transform: translateY(-50px);
}
100% {
opacity: 1;
transform: translateY(0px);
}
}

.song-fade-in {
animation: song-fade-in-animation linear;
animation-timeline: view();
animation-range-start: cover;
animation-range-end: 400px;
}

.main-song-fade-in {
animation: song-fade-in-animation .4s;
}

.navbar-fade-down{
animation: navbar-fade-down-animation .9s;
}
```

We have a suspicion that this may be due to the use of the methods called in .song-fade-in.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the animation issue on the affected displays, then inspect the animation rules around line 375 in Anti-Spotify/frontend/src/App.css and how they are called by SongRows.tsx. Done means the sliding fade-in animations work on the displays where they currently fail without breaking the existing animations.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, typescript
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.