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]: Multiple CSS Declarations in Othello Game #1129

Open
1 task done
divanshiii09 opened this issue Oct 16, 2024 · 0 comments
Open
1 task done

[Bug]: Multiple CSS Declarations in Othello Game #1129

divanshiii09 opened this issue Oct 16, 2024 · 0 comments

Comments

@divanshiii09
Copy link

Give a brief about the bug ✍️

In the style.css file located in the Othello folder of the Games of Your project, there are multiple declarations for several CSS classes, including .board, .cell, .score-container, .cell.empty, .cell.white, and .message-container. This redundancy can lead to confusion regarding which styles are applied, potentially resulting in inconsistent styling throughout the application.

Screenshots are attached to illustrate the duplicate declarations for your reference.

First Occurrence:

First Occurrence 1 First Occurrence 2

Second Occurrence:

Second Occurrence 1 Second Occurrence 2

Third Occurrence:

Third Occurrence 1 Third Occurrence 2

What is the expected behavior? 🤔

Each CSS class should have a single, clear declaration in the style.css file to maintain clarity and prevent conflicts. This will ensure that styles are applied consistently and make the codebase easier to read and maintain.

Provide step by step information reproduce the bug 📄

  1. Navigate to the following directory:
    MultiPlayer-Games/Othello

  2. Open the style.css file.

  3. Search for the following classes:

    • .board
    • .cell
    • .score-container
    • .message-container
  4. Observe that multiple declarations exist for these classes, indicating a duplication of styles.

Select program in which you are contributing

GSSoC24, Other

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant