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

UI Bug: Left Portion Scrolls with Right Portion on Login Page #2617

Closed
MohitMaulekhi opened this issue Dec 7, 2024 · 2 comments
Closed

UI Bug: Left Portion Scrolls with Right Portion on Login Page #2617

MohitMaulekhi opened this issue Dec 7, 2024 · 2 comments
Labels
bug Something isn't working unapproved

Comments

@MohitMaulekhi
Copy link

Bug
I encountered a UI issue on the login page. The left portion is not independent of the right portion. As a result, while scrolling the right portion, the left portion moves along with it, which is not the intended behavior.

To Reproduce
Steps to reproduce the behavior:

  1. Navigate to the login page.
  2. Scroll the right portion of the page.
  3. Observe that the left portion scrolls along with the right portion.

Expected behavior
The left portion should remain static while scrolling the right portion.
Screenshot 2024-12-07 190526

Actual behavior
I have fixed this issue by making both portions independent of each other. This helps to make right portion static as in the image given below
Screenshot 2024-12-07 214214
Screenshot 2024-12-07 214226

Additional details
This fix ensures that the left portion remains static while scrolling the right portion, improving the overall user experience on the login page.

Request to be Assigned
Could you please assign this issue to me? I would like to work on it and submit a PR with the fix.

@MohitMaulekhi MohitMaulekhi added the bug Something isn't working label Dec 7, 2024
Copy link

github-actions bot commented Dec 7, 2024

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

@palisadoes
Copy link
Contributor

We are now focusing on three types of issues as priority areas:

  1. The improvement in the reliability of our code base. There are many issues created to test existing code. It is a good place to start if you want to understand the operation of various apps. When you submit PRs, we automatically check to see whether the code you submitted has been covered by testing and that each file meets the minimum standard level of the repository as a whole. You won’t be able to avoid understanding testing regimes to contribute to Talawa.
  2. The fixing of bugs and features that seriously hamper the user from using the application. The apps have various shortcomings. The most obvious ones are where the apps do not work as expected. For example buttons that don’t work, errors or messages that are not displayed to make the user understand what to do and many more. Think of any difficulty you have had in getting things working, there could be a bug there waiting for you.
  3. Coding of screens for issues created by our Contributor team based on our soon to be updated design guide. This may include updates to existing screens.
  4. The creation of additional or updated documentation that helps with improving both the experience of the end user and the various GitHub contributors who support the development of our software. This would include user guides.

We will only be accepting feature issues for deficiencies that are obviously lacking in the apps. These are things that make it very difficult to operate the apps. Even so, the PRs will still require you to understand testing as stated before.

Cosmetic changes that require only a few lines of code, or relate to screen sizes unlikely to be used are not acceptable under this policy.

Closing

@palisadoes palisadoes closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unapproved
Projects
None yet
Development

No branches or pull requests

2 participants