{% extends "base.html" %} {% block title %}Inventory · foilstack{% endblock %} {% block status %}{{ totals.count }} in stock · {{ totals.market|money }} at market{% if totals.sold_rows %} · {{ totals.sold_rows }} sold, {{ totals.realised|money }} realised{% endif %}{% endblock %} {% block screen %} {# Nowrap for the reason the listing run is: at 1000px, the width the README animation is captured at, anything else on this bar pushed the primary button onto a row of its own and the filter row below it then read as three rows of chrome above the table. The give is the search box, which both takes the leftover width and is the only thing here still usable narrower — which is why the status chips went down to the filter row and not beside it. #}
{# Every way of narrowing the screen, on one row: which rows are in play, then the facets. The status chips moved down out of the bar when the search box grew to fill it — they are a filter, they belong beside the other filters, and the alternative was a bar that wrapped at the width the README animation is captured at. The facets are menus rather than rows of chips because a row painted every value it could fit and then admitted to hiding the rest: at ten sets that is four lines of chrome above the table, and at a hundred it is a "+90" the seller cannot click. A menu shows one value closed and all of them open. The cost is that a closed control has to say what it is doing, which is what `any_label` and the picked-value summary are for — a filter you have to open a menu to discover is the same fault the old row avoided by shouting. #}