Making WordPress.org

Opened 2 years ago

Closed 2 years ago

#6098 closed defect (bug) (fixed)

Body width is not proper(Found in Chrome Browser)

Reported by: kajalgohel's profile kajalgohel Owned by:
Milestone: Priority: normal
Component: Trac Keywords: has-patch needs-testing
Cc:

Description

In the responsive design is messed up for the below url, Issue is happning at 1136px resolution and below, the body width is not set, when we go to smaller device the body is shrink totally. It is not look good in mobile devices.

https://core.trac.wordpress.org/tickets/latest
https://core.trac.wordpress.org/tickets/active

Attachments (5)

#6098.patch (539 bytes) - added by kajalgohel 2 years ago.
Screenshot 2022-02-14 at 2.20.50 PM.png (1.5 MB) - added by kajalgohel 2 years ago.
Screenshot of issue
Screenshot 2022-02-14 at 2.21.16 PM.png (1.4 MB) - added by kajalgohel 2 years ago.
Screenshot of issue
#6098.2.patch (719 bytes) - added by kajalgohel 2 years ago.
Add Patched for responsive (640px and below)
6098.3.patch (446 bytes) - added by nidhidhandhukiya 2 years ago.
i have another solution for this we can add a scroll starts from the screen 1200 so that we can solved this issue globally.

Change History (12)

@kajalgohel
2 years ago

@kajalgohel
2 years ago

Screenshot of issue

@kajalgohel
2 years ago

Screenshot of issue

@kajalgohel
2 years ago

Add Patched for responsive (640px and below)

@nidhidhandhukiya
2 years ago

i have another solution for this we can add a scroll starts from the screen 1200 so that we can solved this issue globally.

#2 @nidhidhandhukiya
2 years ago

  • Component changed from General to WordPress.org Site
  • Keywords needs-testing added

#3 @dd32
2 years ago

  • Component changed from WordPress.org Site to Trac
  • Priority changed from high to normal

See also #4917 which has covered a lot of the Trac responsive issues.

I haven't reviewed the changes proposed here.

#4 follow-up: @kajalgohel
2 years ago

@dd32

Please review this changes(patch) which is displayed here because the issue remain same, or should I update this same patch for the #4917 issue ?

#5 in reply to: ↑ 4 ; follow-up: @dd32
2 years ago

Replying to kajalgohel:

Please review this changes(patch)

Apologies for not being clear - I was referencing the other issue here, and stating that I haven't reviewed the proposed changes, not that I was ignoring it.

#6 in reply to: ↑ 5 @kajalgohel
2 years ago

Replying to dd32:

Apologies for not being clear - I was referencing the other issue here, and stating that I haven't reviewed the proposed changes, not that I was ignoring it.

Thanks For your response. Now I getting the point.

#7 @dd32
2 years ago

  • Resolution set to fixed
  • Status changed from new to closed

See [11609]

Note: See TracTickets for help on using tickets.