mozilla/treeherder-ui — pull request #226 by tojonmz (2014-10-09 19:13:46+00:00)
Title: Bug 1080669 - Clean up resultset boundary and optimize page space

This fixes Bugzilla bug [1080669](https://bugzilla.mozilla.org/show_bug.cgi?id=1080669).

The current resultset boundary was indented twice, due to several pieces of markup which both inherit the `.result-set` class.

![resultsetmargins](https://cloud.githubusercontent.com/assets/3660661/4582011/f9973592-4fe4-11e4-9979-3f040c915324.jpg)

So instead we remove the padding and layout the elements so they are more visually aligned with the adjacent UI above (watched repo, Treeherder main logo). This has the additional benefit of giving us little more page space for revisions and jobs in each resultset.

![resultsetmarginsproposed](https://cloud.githubusercontent.com/assets/3660661/4582026/30b9951a-4fe5-11e4-8db0-02d1638d0784.jpg)

While I was there, I did a little tweaking to the resultset row, trying to clean up some buttons.

* making the toggle revisions and total job count buttons not abut each other
* making the total job count button accommodate 1,000+ job counts

Here is the final look in full:

![resultsetmarginsproposedfull](https://cloud.githubusercontent.com/assets/3660661/4582180/53bed498-4fe6-11e4-8316-de9f0668f12a.jpg)

My only question, is should we remove [this now unused class](https://github.com/mozilla/treeherder-ui/blob/909334b191321a093101aa56e4933f7d904a6a08/webapp/app/partials/main/jobs.html#L46) or leave it in for potentially changes later? As I've noticed a few other orphans in the markup with no connected css.

Everything looks reasonable on Firefox and Chrome at various browser widths, single resultset views, toggled job states, and similar workflows. If you guys can check it on OSX that would be great.

Tested on Windows:
FF Release 32.0.3
Chrome Latest Release 37.0.2062.124 m

Adding @camd and @wlach for review and @edmorley for visibility.