[Bug]:UI responsiveness

Question

[Bug]:UI responsiveness

CedricNdong opened this issue a year ago · 14 comments

What happened?
While examining the web interface on various devices, I've noticed a significant issue in terms of responsiveness. Specifically, the problem exists on the right-hand side container of the page which seems to go out of bounds when viewed on certain screen sizes or devices.

Expected result:

The content of the page should adjust according to the screen size, allowing users to view and interact with the entire content within the bounds of the screen without having to scroll horizontally. All containers should fit within the viewport width.

Actual result:

The right container does not resize properly. As a result, part of its content extends beyond the visible screen bounds.

Add screenshots
Screenshot on desktop screen size (768 x 814)

Possible cause:

There might be CSS styling issues causing the right container to not resize appropriately on smaller screens, but further investigation is needed to ascertain the exact root cause.

Impact:

This issue affects usability on certain devices, potentially hindering user interaction and overall user experience.

What browsers are you seeing the problem on?

Chrome, Microsoft Edge, Brave

Record

I want to work on this issue

iushsh commented 6 months ago

Aayush

Answer 1 · 2023-06-09T18:56:12.000Z

Hello, I would like to work on this issue.

Answer 2 · 2023-06-12T09:30:16.000Z

Is this issue still open?

Answer 3 · 2023-06-12T10:35:35.000Z

Is this issue still open?

Yes, it is still open. You can fix and submit a PR request.

Answer 4 · 2023-06-13T14:06:54.000Z

I think so this solve the issue i flex wrap the "flex flex row" div and now the content is adjusting according to screen size

Answer 5 · 2023-07-13T11:34:40.000Z

@CedricNdong Is anyone currently working on this? If not, would you be able to assign it to me so that I can try to solve it?

Answer 6 · 2023-07-14T08:39:50.000Z

could you ple assign me this issue

Answer 7 · 2023-07-14T09:04:05.000Z

Hello @Jyoticharan @SAMI-THAKUR @udaySuryaP of course! You can Work on it and create a PR.

Answer 8 · 2023-07-18T04:35:03.000Z

Hey,
Is this issue still open ?

I would like to solve the issue

Answer 9 · 2023-07-21T05:17:27.000Z

link of the repository?

Answer 10 · 2023-07-25T05:18:57.000Z

Hi @CedricNdong maybe PR #611 fixed this issue

Answer 11 · 2023-08-17T19:31:16.000Z

Is this issue still open, If it is can I start working on it?

Answer 12 · 2024-01-18T18:44:44.000Z

@CedricNdong is this issue still open?

Answer 13 · 2024-02-09T22:01:22.000Z

@CedricNdong this thing is already fixed can you please mark this as closed