Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Fixtures competition widget status CSS #1767

Closed
4 of 12 tasks
jonsnowpt opened this issue Oct 17, 2023 · 7 comments
Closed
4 of 12 tasks

[Bug]: Fixtures competition widget status CSS #1767

jonsnowpt opened this issue Oct 17, 2023 · 7 comments
Assignees
Labels
🐞 [A] bug Something isn't working. Needs to be looked at. 🎨 Frontend

Comments

@jonsnowpt
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

🐞 Describe the bug

The status CSS is not correct:

Screenshot 2023-10-17 at 16 15 48

🤔 Expected Behavior

Screenshot 2023-10-17 at 16 16 09

What environment is the bug/issue detected in.

  • Production (scores.betarena.com)
  • Development

What browsers are you seeing the problem on?

  • Firefox
  • Chrome
  • Safari
  • Microsoft Edge
  • Brave
  • Opera

What device/platform can the problem be seen?

  • 📱 Mobile
  • 💻 Tablet
  • 🖥️ Laptop/Desktop

Steps To Reproduce

https://betarena-scores-platform.herokuapp.com/football/river-plate-boston-river-18942277

Console Logs (if any)

No response

Anything else?

No response

@jonsnowpt jonsnowpt added 🐞 [A] bug Something isn't working. Needs to be looked at. 🎨 Frontend labels Oct 17, 2023
@jonsnowpt jonsnowpt moved this to Todo in Betarena Scores Oct 17, 2023
@migbash
Copy link
Collaborator

migbash commented Oct 19, 2023

Note
Already Corrected addressed as part of issue ➤ #1765 .
Awaiting 🚀 deployment.

@migbash migbash added this to the [FEATURE]: Competitions milestone Oct 19, 2023
@migbash migbash moved this from Todo to Staging in Betarena Scores Oct 19, 2023
@migbash
Copy link
Collaborator

migbash commented Oct 19, 2023

Note
Live on dev from v880.

@migbash migbash removed the status in Betarena Scores Oct 19, 2023
@migbash migbash moved this to Testing in Betarena Scores Oct 19, 2023
@migbash migbash assigned jonsnowpt and unassigned migbash Oct 19, 2023
@jonsnowpt
Copy link
Contributor Author

@migbash

Here are still incorrect:

Image

@jonsnowpt jonsnowpt moved this from Testing to Todo in Betarena Scores Oct 19, 2023
@jonsnowpt jonsnowpt assigned migbash and unassigned jonsnowpt Oct 19, 2023
@migbash
Copy link
Collaborator

migbash commented Oct 19, 2023

Note
Corrected addressed as part of issue ➤ #1785 .
Awaiting 🚀 deployment.

@migbash migbash moved this from Todo to Staging in Betarena Scores Oct 19, 2023
@migbash
Copy link
Collaborator

migbash commented Oct 19, 2023

Note
Live on dev from v883.

@migbash migbash moved this from Staging to Testing in Betarena Scores Oct 19, 2023
@migbash migbash assigned jonsnowpt and unassigned migbash Oct 19, 2023
@jonsnowpt
Copy link
Contributor Author

jonsnowpt commented Oct 19, 2023

@migbash

The dark color should have a 50% passthrough.

@jonsnowpt jonsnowpt moved this from Testing to Todo in Betarena Scores Oct 19, 2023
@migbash migbash moved this from Todo to Staging in Betarena Scores Oct 19, 2023
@migbash migbash moved this from Staging to Testing in Betarena Scores Oct 19, 2023
@migbash
Copy link
Collaborator

migbash commented Oct 19, 2023

Note
Corrected, awaiting 🚀 deployment.
Live on dev from v884.

@github-project-automation github-project-automation bot moved this from Testing to Done in Betarena Scores Oct 20, 2023
migbash added a commit that referenced this issue Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 [A] bug Something isn't working. Needs to be looked at. 🎨 Frontend
Projects
Archived in project
Development

No branches or pull requests

2 participants