Repository navigation
v0.1.7
Draw every offered width from the list the endpoint serves
A declared width was emitted literally, so width: 1200 asked for 1200 and
2400 — two widths no allow-list contains, and a srcset where those entries
400. Widths now round up onto a fixed ladder, which also gains a small
rung set so a 48px avatar stops being offered 640.
Rounding up rather than down: down is how a dense screen is handed fewer
pixels than it can show, and the softness is hard to attribute later.
Add Image and Picture, responsive by default
A bare ships desktop pixels to a phone and reserves no space
until it arrives. Both are fixed by attributes nobody writes by hand, so
these components write them: a srcset of a dozen widths, a matching
sizes, width/height for the ratio, loading and decoding.
The bytes come from a resolver the app installs, defaulting to the
/__image endpoint @c9up/prism registers — a component that imported an
image processor would drag a native module into a package whose only
peer is Aurora.
One deviation from the usual ladder-and-filter, commented where it
lives: a constrained image also offers the source width itself, so a
500px source displayed at 400 is not handed to a dense screen upscaled.
Changes since v0.1.6.