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

Duplicate Property Assignment for position in style.css #996

Closed
divanshiii09 opened this issue Oct 15, 2024 · 2 comments · Fixed by #1037
Closed

Duplicate Property Assignment for position in style.css #996

divanshiii09 opened this issue Oct 15, 2024 · 2 comments · Fixed by #1037

Comments

@divanshiii09
Copy link
Contributor

Description:
I have discovered an issue in the style.css file where the position property is assigned multiple times for the .layout-container class. This can lead to unexpected behavior in the layout and should be addressed to improve the code quality.


Issue Details:

  • File: style.css
  • Container: .layout-container (on line 910)
  • Duplicate Property: position

Screenshot:
WhatsApp Image 2024-10-15


Expected Behavior:
Each CSS property should only be assigned once per container to avoid conflicts. The second assignment of position will override the first, leading to potential layout issues and confusion.


Proposed Solution:

  • Remove the duplicate position property. Determine the intended value (either relative or sticky) and keep only that assignment in the code.

Additional Information:
Fixing this issue will enhance the maintainability of the code and ensure that the styling behaves as expected.


Copy link

Thanks @divanshiii09 for raising this issue! We'll look into it.We hope you have made sure that a similar issue doesnt exist , if it does, kindly ask to be assigned on that issue

@divanshiii09
Copy link
Contributor Author

@ANSHIKA-26 I would love to work on this issue, please assign it to me

ANSHIKA-26 added a commit that referenced this issue Oct 16, 2024
Bugfix: Correct Navbar Positioning Issues in style.css (#996)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants