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 : Bug Report: Notification Adjustment on Mobile #2799

Closed
harshal050 opened this issue Dec 24, 2024 · 1 comment
Closed

Bug Report : Bug Report: Notification Adjustment on Mobile #2799

harshal050 opened this issue Dec 24, 2024 · 1 comment
Labels
bug Something isn't working good first issue Good for newcomers ui/ux issue related and being worked with the figma file of the Admin UI unapproved

Comments

@harshal050
Copy link

Describe the bug
Notifications on mobile are not taking up the entire top space as intended, leading to an incomplete or misaligned display.

To Reproduce
Steps to reproduce the behavior:

1.Open the application on a mobile device.
2.Trigger a notification.
3.Observe the notification's layout and positioning.
4.Notice that it does not occupy the entire top space as expected.

Expected behavior
The notification should expand to take up the entire top space on the mobile screen, ensuring proper alignment and visibility.

Actual behavior
The notification appears misaligned or does not fully occupy the top space, affecting the user experience.

video

Recording.2024-12-24.233708.mp4
@harshal050 harshal050 added the bug Something isn't working label Dec 24, 2024
@github-actions github-actions bot added ui/ux issue related and being worked with the figma file of the Admin UI unapproved good first issue Good for newcomers labels Dec 24, 2024
@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 24, 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 good first issue Good for newcomers ui/ux issue related and being worked with the figma file of the Admin UI unapproved
Projects
Development

No branches or pull requests

2 participants