In order to properly implement the filters in the all layers, all targets and all machines pages, we need the filter counters to update without refreshing the whole page whenever you add or remove a layer from the project. In order to this without ugly hacks involved, we should implement these tables using the AngularJS framework.
We need to organically treat all table-based pages as mini-applications, instead of relaying on hacks to provide proper information display and update. Currently - - The page size, ordering, filtering and search terms are saved through cookies and enforced through page reload; these should be backed by modeled data as to maintain consistency of display. - On actionable items, the buttons are drawn after ajax requests, and filter options and labels are updated by DOM modification, instead of being supported by proper models and controllers in the page DOM editing without model support leads to unmaintable and unfixable code, which should be avoided. Also, transitioning the pages to the angular framework will provide a better user experience through reducing page loading times, and maintain user context through avoiding browser refresh.
I propose wontfix on this one as I don't think the current page implementations are really adaptable to having a hybrid of Angular, js, jquery, django template and custom view generation. However I'm not saying that there shouldn't be a time to re-asses the technologies/architecture/design of toaster but this is much bigger than the scope of this bug.