When screen width goes below 1076px the menu disappears, being replaced by a button. Clicking the button displayed the default twitter bootstrap, which was pretty icky. Now it displays a much nicer slide in menu from the right.
Improved unreachable host count in tasks status bar. Once a host is unreachable it shows as missing in subsequent tasks, which is the expected result as it is skipped but not really marked as skipped.
When user switches from a search filter using an input field to one using a drop-down the bottom margin no longer disappears. The disappearing margin caused an unpleasant bounce effect.
Added 5px to navbar-collapse. Fixes FF active/focus border touching the logo. Try as I might, I cannot get FF 30 to stop with the dashed boarder around the active menu item.
Job tasks now include an unreachable count and %. Change unreachable color from grey to a different shade of red. While live events are happening host name filter is disabled and status filter is available. Created a custom status filter that accounts for live event processing. While live event processing is active angular filtering on status is disabled for tasks and plays, otherwise no tasks or plays would show up. However, status filtering does apply to host results and host summaries during live event processing.
Changed 'successful' to 'OK' throughout the page. Also fixed status tool tip text on unreachable hosts to be 'Unreachable' rather than 'failed'. Fixed tool tips on Plays and Tasks so that they updated in sync with status changes.
For SCM update and inventory sync job types, clicking on job details now gives you the log viewer dialog rather than attempting to load the job detail page and ending in error.
Changed host query from excluding things where host_id not null to including all runner events. This is to accommodate the temporary creation of hosts during a playbook run.
Attempted to remove the dashed outline around active or focused links. CSS outline property is supposed to control this. However, FF ignores and adds a dashed line anyway. Seems like a FF bug.
Fixed endless scroll, both up and down. It now models the Jenkins behavior. If live events are happening, it captures and displays them, always auto-scrolling down. If user srolls up, live events continue to be captured but auto-scrolling is suspended. If user scrolls all the way back down to bottom, auto-scrolling resumes.
