Making WordPress.org

Opened 7 years ago

Closed 2 years ago

#3118 closed defect (bug) (duplicate)

Trac: Improve mobile styling on report pages

Reported by: mitraval192's profile mitraval192 Owned by:
Milestone: Priority: normal
Component: Trac Keywords:
Cc:

Description

I found the "https://meta.trac.wordpress.org" site is not looking properly on the mobile device.

Attachments (2)

meta.trac.wordpress.org.png (31.2 KB) - added by mitraval192 7 years ago.
Displaying white space on the right side of the page.
responsive-table.jpg (51.6 KB) - added by birgire 7 years ago.
Example of a responsive trac table

Download all attachments as: .zip

Change History (10)

@mitraval192
7 years ago

Displaying white space on the right side of the page.

#1 @SergeyBiryukov
7 years ago

  • Component changed from General to Trac

#2 @mitraval192
7 years ago

Regarding this issue, we need to add one div on above the "<table class="listing tickets">".

and add to below CSS to that div.

div.CLASS_NAME { 
   width: auto;
   overflow: scroll;
}
Version 0, edited 7 years ago by mitraval192 (next)

#3 @SergeyBiryukov
7 years ago

  • Summary changed from Mobile Responsive issue to Trac: Improve mobile styling on report pages

@birgire
7 years ago

Example of a responsive trac table

#5 @birgire
7 years ago

In responsive-table.jpg we have an example of a responsive trac table, where each column has full width:

table.listing th, table.listing td {
    display: block;
}


where we would wrap this in a css mobile media query.

This would also need extra labels, only visible on mobile, for the column names in each row.

#7 @vladytimy
3 years ago

Based on this proposal made by @birgire there is a similar proposal here (3rd item):

https://meta.trac.wordpress.org/ticket/4917#comment:17

This is a 4 part patch that tries to bring better responsiveness for Trac reports. Your feedback and testing would be much appreciated. Thank you!

#8 @dd32
2 years ago

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

This might be improved with [11610], but regardless, I'm going to close this as a duplicate of #4917

Note: See TracTickets for help on using tickets.