<feed xmlns='http://www.w3.org/2005/Atom'>
<title>luci/themes/luci-theme-footstrap/root, branch master</title>
<subtitle>Lua Configuration Interface (mirror)</subtitle>
<id>https://git.openwrt.org/project/luci/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/luci/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/luci/'/>
<updated>2026-10-10T13:02:37Z</updated>
<entry>
<title>luci-theme-footstrap: dedupe js and drop pre-24.10 paths</title>
<updated>2026-10-10T13:02:37Z</updated>
<author>
<name>Ivan Kvashonkin</name>
</author>
<published>2026-10-08T09:11:17Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/luci/commit/?id=81b0680cc76c42a18756448fdad02535e3596e5d'/>
<id>urn:sha1:81b0680cc76c42a18756448fdad02535e3596e5d</id>
<content type='text'>
Shared attribute and activation helpers move into fs-widgets, axes are
exported as objects and the footer partial is inlined. Drops fallbacks
for luci-base older than 24.10 and guards for elements the chrome always
renders. It also drops module exports nothing in the tree reads.

Signed-off-by: Ivan Kvashonkin &lt;vizzlef@gmail.com&gt;
</content>
</entry>
<entry>
<title>luci-theme-footstrap: sync with release 0.14.13</title>
<updated>2026-09-20T11:32:55Z</updated>
<author>
<name>Ivan Kvashonkin</name>
</author>
<published>2026-09-18T22:06:03Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/luci/commit/?id=c8a49e1947971291dd3acc17a9356acf03941b3b'/>
<id>urn:sha1:c8a49e1947971291dd3acc17a9356acf03941b3b</id>
<content type='text'>
Appearance becomes a page of its own under System, replacing the tab
the theme stapled onto luci-mod-system's form, and the reader's scroll
position now survives a poll refill on every engine, Back included.
Adds a fifth colourway, a movable content-width cap, Overview cards
that collapse from the keyboard and meters that colour by their own
reading. The wallpaper uploads move out of fs-prefs.js into their own
module and the SVG sanitiser is hardened; the pattern is now served by
a CGI handler with CSP 'none', sandbox and nosniff rather than a /www
symlink a browser will run as a document. postinst and postrm no
longer call `rpcd reload`, which could permanently drop an unrelated
rpcd plugin.

Signed-off-by: Ivan Kvashonkin &lt;vizzlef@gmail.com&gt;
</content>
</entry>
<entry>
<title>luci-theme-footstrap: simplify uci-defaults</title>
<updated>2026-08-21T04:23:57Z</updated>
<author>
<name>Ivan Kvashonkin</name>
</author>
<published>2026-08-20T17:50:21Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/luci/commit/?id=af3993e12e2bd07c32fb0b7943700ac2cc88f6b1'/>
<id>urn:sha1:af3993e12e2bd07c32fb0b7943700ac2cc88f6b1</id>
<content type='text'>
The script registered the theme and then cleaned up after every version of
it that ever shipped: eight legacy theme names, four legacy media paths,
the old top-bar layout carried into luci.main.footstrap_layout, two
downloaded wallpapers, a pre-0.12.1 fonts/ directory, a fallback to
bootstrap when the active theme's files were missing, /etc/config/footstrap
creation that the shipped conffile already covers, and a marker file to
tell a fresh install from an upgrade. All of it served installs that
predate the version merged into this tree.

OpenWrt expects a sysupgrade rather than a package upgrade, so file
leftovers go with the image, and the cleanup worth doing is config. What is
left is the registration, the three symlinks that expose the admin's
uploads out of /etc, and the same fresh-vs-upgrade rule the other themes
here use: mediaurlbase is written only in the run that first added
luci.themes.Footstrap.

postrm loses the same eight-name list, the layout key and the marker
directory.

Behaviour was compared with the old script on 25.12/apk and 24.10/opkg: a
fresh install with a theme already chosen registers and does not switch, an
upgrade changes nothing, a fresh install with no mediaurlbase activates the
theme, a second run in the same install is a no-op, postrm "upgrade"
changes nothing and postrm "remove" hands the UI back to bootstrap.

Signed-off-by: Ivan Kvashonkin &lt;vizzlef@gmail.com&gt;
</content>
</entry>
<entry>
<title>luci-theme-footstrap: add new theme</title>
<updated>2026-08-20T15:59:30Z</updated>
<author>
<name>Ivan Kvashonkin</name>
</author>
<published>2026-08-03T11:25:11Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/luci/commit/?id=6f08de768f4ddc3701144680b833773f50252c51'/>
<id>urn:sha1:6f08de768f4ddc3701144680b833773f50252c51</id>
<content type='text'>
A standalone theme for OpenWrt 24.10 and newer. It ships no CSS framework
and depends on nothing but luci-base: the package is the server chrome
(ucode templates), one stylesheet and a set of theme JS modules, while
every page is still rendered by luci-base's own view JS.

One chrome morphs between a collapsible sidebar and a top bar, chosen by
the user and remembered client-side. Light and dark modes, a palette and a
density axis are applied before the first paint, so a reload never flashes
the previous colours. A menu search covers the rendered tree, and a
client-side router swaps the view without a full document load, refusing
to reuse a document an app's own stylesheet has invaded.

Third-party luci-app-* packages are the constraint it is built around: the
chrome is namespaced (fs-*, --fs-*, [data-fs-chrome]) and is defended by
not matching an app's selectors, while .cbi-* and #view stay shared
surfaces an app is entitled to win on. The theme's own settings page is
drawn with stock .cbi-value rows, ui.Select and ui.RangeSlider.

The stylesheet is generated from a layered source kept in the theme's own
repository and committed here as one file, the way the other themes carry
theirs. The theme carries no webfonts: the font stacks name Manrope and
JetBrains Mono first and the system stack after, so a machine with either
installed uses it and one without falls through silently.

A router may name fonts of its own on top of that fallback, through three
UCI options in footstrap.settings that the templates read back: font_sans
and font_mono are font-family stacks printed into an unlayered &lt;style&gt;,
and `fonts` is the md5 of an @font-face sheet the admin installs under
/etc/footstrap/fonts, which uci-defaults links under /www and keep.d
preserves across sysupgrade. The package installs no faces and fetches
nothing at run time; it only serves what is already there.

A web manifest and one app icon ship with the theme, so the interface can
be installed to a phone's home screen. Both are static files — a theme may
not register a dispatcher node — which fixes start_url at uhttpd's default
/cgi-bin/luci/ and the splash colour at the default palette's; the manifest
is served as .json because uhttpd's compiled-in MIME map has no entry for
.webmanifest.

The client router looks up every luci-base surface it calls before it wires
anything, and on a miss logs which name is gone and stays off, leaving the
plain server-dispatched interface rather than a half-working client one.

Where the browser has no scroll anchoring of its own, the theme keeps the
reader's place itself: a poll tick that changes the height of anything
above the reader moves the page under them on WebKit, which never
implemented it. The capability decides, never a browser name, so where the
engine already anchors, this stays out of the way and nothing is corrected
twice. The two page-specific modules are required on the pages that use
them rather than on every page.

Signed-off-by: Ivan Kvashonkin &lt;vizzlef@gmail.com&gt;
</content>
</entry>
</feed>
