#217: Make Bloodhound's layout responsive
-------------------------+-------------------------------------------------
Reporter: jdreimann | Owner: matevzb
Type: | Status: closed
enhancement | Milestone: Release 5
Priority: major | Version:
Component: ui design | Keywords: ui, responsive, bootstrap, mobile,
Resolution: fixed | tablet, desktop
-------------------------+-------------------------------------------------
Comment (by rjollos):
While working on #271, I noticed that in [1442158] the `#content` id was
moved from the first nested div on the rendered page to the div that
encloses the ticket properties. The convention in Trac is to have
`#content` on the outermost div in the template. Examples:
*
[http://trac.edgewall.org/browser/tags/trac-1.0.1/trac/ticket/templates/ticket.html?marks=121#L116
ticket.html]
*
[http://trac.edgewall.org/browser/tags/trac-1.0.1/trac/wiki/templates/wiki_view.html?marks=30#L29
wiki_view.html]
*
[http://trac.edgewall.org/browser/tags/trac-1.0.1/trac/search/templates/search.html?marks=24#L23
search.html]
*
[http://trac.edgewall.org/browser/tags/trac-1.0.1/trac/ticket/templates/roadmap.html?marks=14#L13
roadmap.html]
[[Image(TicketPage.png)]]
[[Image(MilestonePage.png)]]
In the two images, the div with the `#content` id is highlighted.
Keeping `#content` on the outermost div of each template makes some CSS
more convenient. It seems to be okay to move it to the enclosing div on
the ticket page, but I just wanted to check to be sure before making the
change.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/217#comment:19>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
