[wp-trac] [WordPress Trac] #24165: Re-skinning Trac 1.0

[WordPress Trac]

#24165: Re-skinning Trac 1.0
--------------------------------+----------------------------
 Reporter:  nacin               |       Owner:
     Type:  enhancement         |      Status:  new
 Priority:  high                |   Milestone:  WordPress.org
Component:  WordPress.org site  |     Version:
 Severity:  minor               |  Resolution:
 Keywords:                      |
--------------------------------+----------------------------

Comment (by nacin):

 Replying to [comment:27 bpetty]:
 > It looks like we break out of max-width for many of the reports, but we
 still don't for
 [http://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&component=Filesystem&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=changetime&col=reporter&col=keywords&order=priority
 custom queries] or any reports based on custom queries (like
 [http://core.trac.wordpress.org/report/46 report 46]). Can we get that
 fixed?

 I actually had it set up to "break out" on a few other pages: query,
 browser, attachments (uploaded patches), and changesets. See
 [http://core.trac.wordpress.org/changeset/31/meta 31/meta]. ocean90
 convinced me it wasn't needed for code. That left /query. It occurred to
 me that queries were almost always custom by a user, and probably wouldn't
 need an absolute ton of room. Report 46 happens to be the only non-SQL
 report we have. I'm happy to add them back for queries if that is what the
 consensus is.

 Sergey: Fixing.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24165#comment:29>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software