@artstorefronts/arthelper-nav 0.1.0-alpha.5 → 0.1.0-alpha.6

package/README.md

@@ -190,23 +190,12 @@ Peer dependencies (from `package.json` — install these yourself, they are not
 }
 ```
 
-> **Getting a change released.** There is no tag and no manual release step: bump the
-> version in `packages/nav/package.json` in the PR that changes the package, and merging
-> to `develop` publishes it. CI publishes only when that version is absent from the
-> registry, and a PR that changes the published surface while leaving the version alone
-> fails its own check — so a change cannot quietly land without reaching you.
->
-> **Testing an unreleased change.** Link the workspace, or use a path dependency:
->
-> ```bash
-> cd packages/nav && yarn link
-> cd ../../../<satellite> && yarn link @artstorefronts/arthelper-nav
-> ```
->
-> `react` and `react-dom` are peer dependencies, so make sure the satellite's bundler
-> resolves a single copy of React — a linked package pulling in its own is the usual
-> cause of the duplicate-React hooks error. `npm pack` plus installing the tarball avoids
-> that failure mode entirely and resolves more like the real thing.
+> **Need a change to the bar itself?** Its look, layout and behaviour ship in this package
+> rather than being configurable — see [Theming and the wordmark](#theming-and-the-wordmark)
+> — so changing them means a new release. Ask the ArtHelper team; releases are automatic and
+> quick. What you _can_ change without one is which apps appear, in what order and pointing
+> where: that lives in the config row, editable from ArtHelper's admin screen and picked up
+> on next load.
 
 ## Minimal mounting example
 

package/dist/index.css

@@ -77,10 +77,12 @@
    * the wordmark changing typeface as you move between apps, and any family without a
    * real 600 gets faux-bolded on top.
    *
-   * `-webkit-font-smoothing` is pinned for the same reason: a host that sets
-   * `antialiased` on its body thins the bar's text on macOS, so the same 600 weight
-   * looks lighter in that app than the next. `auto` is the default the design was
-   * approved against.
+   * Both smoothing properties are pinned for the same reason: a host that sets
+   * `antialiased` on its body thins the bar's text on macOS, so the same 600 weight looks
+   * lighter in that app than the next. town-square does exactly that — `<body
+   * className="antialiased">` — and Tailwind's utility sets BOTH `-webkit-font-smoothing`
+   * and `-moz-osx-font-smoothing`, so countering only the webkit half leaves Firefox still
+   * inheriting `grayscale`. `auto` is the default the design was approved against.
    *
    * Set on every root the package renders — the bar, the docked trigger (which lives in
    * the host's own header) and the fixed mobile panel — because only the first of those
@@ -95,6 +97,7 @@
     Arial,
     sans-serif;
   -webkit-font-smoothing: auto;
+  -moz-osx-font-smoothing: auto;
   color: var(--ahsuite-label);
   isolation: isolate;
   visibility: visible;
@@ -388,6 +391,7 @@ span.ahsuite-row {
     Arial,
     sans-serif;
   -webkit-font-smoothing: auto;
+  -moz-osx-font-smoothing: auto;
   flex: 0 0 auto;
 }
 
@@ -466,6 +470,7 @@ span.ahsuite-row {
     Arial,
     sans-serif;
   -webkit-font-smoothing: auto;
+  -moz-osx-font-smoothing: auto;
 }
 
 .ahsuite-panel-head {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@artstorefronts/arthelper-nav",
-  "version": "0.1.0-alpha.5",
+  "version": "0.1.0-alpha.6",
   "description": "The ArtHelper suite navigation bar — a config-driven, cross-origin app switcher.",
   "license": "ISC",
   "type": "module",