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 Report: Unresponsiveness and Overlapping Elements in 'Organization Events' #997

Closed
SURAJ-SHARMA27 opened this issue Oct 21, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@SURAJ-SHARMA27
Copy link

Describe the bug
The issue on the "Organization Events" page arises when the screen width falls below 1400px, causing the site to become entirely unresponsive. The search date calendar shrinks as the screen size decreases, rendering the dates unclearly visible at that dimension. Also, the month and year names overlap with the "Add Event" element. Additionally, when the screen width is below 1400px, a vertical line appears on the far right of the page, which overlaps with the navigation buttons and the "Add Event" button. This unexpected behaviour can significantly impact the user experience.

To Reproduce
Steps to reproduce the behavior:

  1. After login go to manage organization page.
  2. In dashboard page click on view all under upcoming events element.

Expected behavior
The page should be responsive for all screen sizes, and there should be no unwanted elements overlapping each other.

Actual behavior
The site becomes unresponsive when the screen width is <1400px.
The search date calendar shrinks, making dates unclear.
Month and year names overlap with the "Add Event" element.
A vertical line appears, overlapping navigation buttons and the "Add Event" button, affecting user experience.

Additional details
Assign this issue to me

bandicam.2023-10-21.22-19-07-695.mp4
@SURAJ-SHARMA27 SURAJ-SHARMA27 added the bug Something isn't working label Oct 21, 2023
@github-actions
Copy link

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. Stay tuned, we expect these issues to be created during the first week of November 2023. @rishav-jha-mech is leading this process for the Talawa Admin project
  4. The creation of additional our 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.

Closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants