{#- The declarative action list's chip (ADR-0038), rendered through the slot seam like any other filler — so a configured action and a deployment's coded one land in the same rail, in one order, wearing the same chip. The provider computed every href in Python, percent-encoding each substituted value, and this template only places them. `class` is chosen by the surface: the two slots have different rails and the chip belongs to the one it is in. **In a head's row a node's action is its icon where it names one, its label where it does not** (ADR-0127 decision 3): an action with an icon is a square like the head's own buttons, `.is-icon`, the image alone inside it and the label as its tooltip and accessible name, at the head's own glyphs' 16 pixels; one without keeps its label as the small chip it was, since a letter in a square would be a guess on a touch screen. A line's chip keeps the icon beside its label, as it stood. -#} {%- for entry in actions %} {%- if entry.icon and chip == 'node-action' %} {%- else %} {%- if entry.icon %}{% endif %}{{ entry.label }} {%- endif %} {%- endfor %}