@nimblebrain/synapse 0.17.0 → 0.17.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/ui/index.cjs CHANGED
@@ -1557,41 +1557,54 @@ function PageLayout({
1557
1557
  style,
1558
1558
  ...rest
1559
1559
  }) {
1560
- return /* @__PURE__ */ jsxRuntime.jsxs(
1561
- "div",
1562
- {
1563
- style: { display: "flex", flexDirection: "column", gap: "1.1rem", minWidth: 0, ...style },
1564
- ...rest,
1565
- children: [
1566
- /* @__PURE__ */ jsxRuntime.jsx(
1567
- PageHeader,
1568
- {
1569
- crumbs,
1570
- title,
1571
- status,
1572
- actions,
1573
- description,
1574
- descriptionLines
1575
- }
1576
- ),
1577
- tabs,
1578
- toolbar ? /* @__PURE__ */ jsxRuntime.jsx(
1579
- "div",
1580
- {
1581
- style: {
1582
- display: "flex",
1583
- alignItems: "center",
1584
- gap: "0.5rem",
1585
- flexWrap: "wrap",
1586
- minWidth: 0,
1587
- marginBottom: "-0.35rem"
1588
- },
1589
- children: toolbar
1590
- }
1591
- ) : null,
1592
- children
1593
- ]
1594
- }
1560
+ return (
1561
+ // A `<section>`, not a `<div>`, and it is the header below that makes it load-bearing.
1562
+ // `<header>` maps to the `banner` landmark UNLESS it descends from sectioning content, so
1563
+ // a page inside a page — a `PageLayout` in a pane of one — produced TWO banners, both
1564
+ // claiming to head the document. That is the same defect as the app-chrome bar this
1565
+ // layout exists without, one layer down and invisible on screen: it shows up only in the
1566
+ // landmark list a screen-reader user navigates by.
1567
+ //
1568
+ // Scoping it here rather than asking callers to wrap is the point. A consuming app hit
1569
+ // this, diagnosed it, and wrapped its own instance — correct, and not a thing every app
1570
+ // should have to rediscover. An embedded app is not the document anyway: the host owns
1571
+ // the real banner, and what this renders is a section of the host's page.
1572
+ /* @__PURE__ */ jsxRuntime.jsxs(
1573
+ "section",
1574
+ {
1575
+ style: { display: "flex", flexDirection: "column", gap: "1.1rem", minWidth: 0, ...style },
1576
+ ...rest,
1577
+ children: [
1578
+ /* @__PURE__ */ jsxRuntime.jsx(
1579
+ PageHeader,
1580
+ {
1581
+ crumbs,
1582
+ title,
1583
+ status,
1584
+ actions,
1585
+ description,
1586
+ descriptionLines
1587
+ }
1588
+ ),
1589
+ tabs,
1590
+ toolbar ? /* @__PURE__ */ jsxRuntime.jsx(
1591
+ "div",
1592
+ {
1593
+ style: {
1594
+ display: "flex",
1595
+ alignItems: "center",
1596
+ gap: "0.5rem",
1597
+ flexWrap: "wrap",
1598
+ minWidth: 0,
1599
+ marginBottom: "-0.35rem"
1600
+ },
1601
+ children: toolbar
1602
+ }
1603
+ ) : null,
1604
+ children
1605
+ ]
1606
+ }
1607
+ )
1595
1608
  );
1596
1609
  }
1597
1610
  var SidebarCtx = react.createContext(null);