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

Posts are not responisve #1474

Closed
rahulrangers opened this issue Jan 22, 2024 · 3 comments
Closed

Posts are not responisve #1474

rahulrangers opened this issue Jan 22, 2024 · 3 comments
Labels
bug Something isn't working unapproved

Comments

@rahulrangers
Copy link

Describe the bug
when viewing post of an organization the model which appears on clicking the post is not responsive

To Reproduce
Steps to reproduce the behavior:

1.Open Talawa Admin website.
2.Enter an organization.
3.Click on the post.
4.Inspect and check the responsiveness.

Expected behavior
The expected behavior can be the image can be on the middle and text can be down
Actual behavior
Image is not clear

Screenshots

Talawa.Posts.-.Google.Chrome.2024-01-22.16-25-11.mp4
@rahulrangers rahulrangers added the bug Something isn't working label Jan 22, 2024
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.

@NayOoLwin5
Copy link
Contributor

NayOoLwin5 commented Jan 23, 2024

I would like to work on this if this is valid issue

@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 are not acceptable under this policy.

Closing

@palisadoes palisadoes closed this as not planned Won't fix, can't repro, duplicate, stale Jan 23, 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

3 participants