On a 390 px screen the transmit controls were laid out at x=400, off the
side of a tray 354 px wide: present, invisible, and reachable only by a
horizontal scroll with nothing to say it was there. The page scrolled
sideways by a dozen pixels as well.
Three causes, each in a different place.
A container query at the end of the stylesheet re-imposes `flex-wrap:
wrap` on a narrow tray's rows. That is right while a row runs left to
right; below the phone breakpoint the row is a column, and wrapping a
column starts a *second column* — which is what put the transmit
controls beside the tray rather than under it. The rule outranks the
phone one, two classes to its one, and sits later in the file, so it now
excludes itself below that breakpoint rather than being overridden.
The tray is a grid, and a grid column sizes to its content. One row
wider than the screen — the mode picker, six buttons across — dragged
the whole tray out with it. `minmax(0, 1fr)` lets the column be as
narrow as the phone and the rows wrap inside it.
The wavelength and signal-strength readouts are given the width of their
column on narrow screens, but with padding on a content box that is the
column's width plus the padding. Those dozen pixels were the page's
sideways scroll. They are border-box now.
Also: the rig picker was taking 139 px of a 338 px bar, pushing the rest
of the top bar into the overflow menu. It is capped and ellipsised on
phones, with the full name still in the menu it opens.
The map's filter bar, collapsed, keeps both its anchors and shrinks
inside them rather than dropping `left` to be sized by shrink-to-fit,
and no longer asks for a compositing layer it does not need. An
absolutely positioned, backdrop-filtered, composited box sizing itself
from its content is the shape of thing that renders as nothing on an
engine other than the one it was written against — which is what Edge
does with it. Unverified there: this machine has no Edge to test with.
tests/mobile-layout.mjs holds the page to it at 430, 390 and 360 px: no
sideways scroll, nothing laid out past the right edge, the transmit
controls inside the screen, the rig picker within its cap — and the
collapsed filter bar still on screen with a button to bring the filters
back.
The SSTV panel test stamped its picture with a fixed date, which the
panel's own retention window dropped once that date was a day old. It
uses a recent stamp now.
Signed-off-by: Stan Grams <sjg@haxx.space>
A receiver spreads by being linked to, and there was nothing to link to:
the routes carried the tab and nothing else, so "listen to this" could
only ever mean a screenshot and a frequency typed out in a message.
The query string now carries the dial -- rig, frequency, mode and
bandwidth -- in both directions. Opening a link selects the rig, sets
the mode, tunes, then applies the bandwidth: a mode change brings its
own default bandwidth with it, so an explicit bw has to land after it.
Frequencies are read the way someone writes them by hand (7074k,
14.074M) and written back as whole Hz, so what comes out of the address
bar is the same link in canonical form.
After that the address bar keeps up with the dial, which is what makes
it copyable at any moment rather than only at load. It is rewritten
with replaceState -- tuning is not navigation, and a swept dial would
otherwise bury the back button. A link button in the top bar copies
the current link; it folds into the overflow menu when the bar is tight.
Applying a link changes the radio, so an rx session says so instead of
failing control calls one at a time. A tab listening to a virtual
channel leaves the address alone rather than publishing a frequency the
rig is not on, and bw is skipped in both directions on rigs without
filter control, which would only refuse it.
The fixture pinned every state frame to 100 MHz plus jitter to keep
frames distinct, so no test could observe tuning at all. The jitter
moves to the S-meter and the fixture echoes set_freq/set_mode/
set_bandwidth, as it already did for squelch.
Signed-off-by: Stan Grams <sjg@haxx.space>
AIS, VDES and both APRS decoders were listed under the map plugin group
alone, so opening Digital modes and clicking AIS or APRS gave an empty
panel reading "Connected, listening for packets" while the decodes piled
up unprocessed in the plugin runtime. They appeared only if something
had opened the Map tab first, which flushed the queue. There is also a
map-data group naming exactly those four that nothing loads: the loader
is called with tab names and no tab is called map-data.
They load with the tab whose panels they fill now. map-core stays lazy,
since their calls into it are optional and the Map tab can go on paying
for Leaflet by itself.
tests/decode-flow.mjs follows a decode from the wire to the map: an AIS
vessel and an APRS beacon arrive on /decode, and it asserts both panels
fill with the map module confirmed absent, the mini view names the
vessel and offers a pin, following that pin lands on /map centred on the
vessel, and both decoders leave a marker. Nothing exercised any of this
before — the fixture served an empty decode stream, which is how the map
links came to be broken for every decoder at once.
The fixture stamps decodes as it sends them, since the client prunes
anything outside the retention window, and repeats them, since the views
collapse by vessel and need more than one frame to behave.
Signed-off-by: Stan Grams <sjg@haxx.space>
Tuning across a band edge moved the whole page under the cursor: the
band plan strip is in flow, so a range with no allocations collapsed it
from 18px to nothing and dragged every element below it up (measured at
1600x950: overview top 118 to 100, footer 1026 to 1008). It now keeps
its height whenever a band plan could be drawn at all, and only gives it
back when the feature is off, has no data, or there is no spectrum.
The bookmark rail gets the same treatment for consistency, though it
never moved anything — it is absolutely positioned over the top of the
overview. It stays up and blank rather than vanishing.
Which exposes something the rail was already doing wrong: it covers the
top of the plot, and a bare div still takes pointer events, so whenever
bookmarks were in range that band of the overview could not be dragged
or scrolled. Only the chips are targets now.
tests/spectrum-layout.mjs covers this: it streams spectrum frames, tunes
between a band with bookmarks and allocations and one with neither, and
asserts nothing moves and that the rail lets clicks through.
Signed-off-by: Stan Grams <sjg@haxx.space>
sjg