@gjsify/adwaita-core 0.35.0 → 0.37.0

package/lib/types/navigation-view.d.ts

@@ -3,12 +3,12 @@ export interface AdwNavigationPageProps {
     /**
      * `AdwNavigationPage:tag` — unique within one view, or `null` for untagged.
      * `''` is a legal tag: the C tag table is a plain `g_str_hash` table and only
-     * a NULL tag is skipped (add_page:1281).
+     * a NULL tag is skipped (add_page).
      */
     tag?: string | null;
-    /** `AdwNavigationPage:title` — defaults to `''`, never null (adw_navigation_page_init:794). */
+    /** `AdwNavigationPage:title` — defaults to `''`, never null (adw_navigation_page_init). */
     title?: string;
-    /** `AdwNavigationPage:can-pop` — defaults to `true` (adw_navigation_page_init:795). */
+    /** `AdwNavigationPage:can-pop` — defaults to `true` (adw_navigation_page_init). */
     canPop?: boolean;
 }
 /**
@@ -16,7 +16,7 @@ export interface AdwNavigationPageProps {
  * them without re-deriving the cause: `'add'`/`'push'` → `::pushed`, `'pop'` →
  * one `::popped` per entry in {@link NavigationStackChange.popped}, `'replace'` →
  * `::replaced`. `'add'` is split out from `'push'` only because it is the
- * auto-push add_page:1284-1285 performs, which is never animated.
+ * auto-push add_page performs, which is never animated.
  */
 export type NavigationChangeReason = 'add' | 'push' | 'pop' | 'replace';
 /** One stack mutation, as a single payload. */
@@ -31,14 +31,14 @@ export interface NavigationStackChange<P> {
      * The page that was visible before this mutation. `previousVisiblePage !==
      * visiblePage` is exactly the condition under which libadwaita notifies
      * `visible-page` — including the `replace()` corner where the old visible
-     * page was destroyed rather than switched away from (replace:3078-3079).
+     * page was destroyed rather than switched away from (replace).
      */
     previousVisiblePage: P | null;
     /** Why the stack moved. */
     reason: NavigationChangeReason;
     /**
      * The popped pages, TOP-FIRST — `::popped` is emitted in this order.
-     * pop_from_stack:989-994 builds the list with `g_slist_prepend` while walking
+     * pop_from_stack builds the list with `g_slist_prepend` while walking
      * bottom-up, then iterates it forward. Always empty unless `reason` is `'pop'`.
      */
     popped: readonly P[];
@@ -46,20 +46,20 @@ export interface NavigationStackChange<P> {
     removed: readonly P[];
     /**
      * The outgoing visible page, destroyed only once the transition finishes
-     * (pop_from_stack:1007 skips it; transition_done_cb:1042 does it). The
+     * (pop_from_stack skips it; transition_done_cb does it). The
      * renderer hands it back by calling {@link NavigationViewState.finishTransition}.
      */
     removeAfterTransition: P | null;
     /**
-     * Whether this transition animates. `false` for the auto-push (add_page:1285),
-     * for every `replace()` (replace:3075), and whenever there is no outgoing page
-     * to slide away from (switch_page:857-858).
+     * Whether this transition animates. `false` for the auto-push (add_page),
+     * for every `replace()` (replace), and whenever there is no outgoing page
+     * to slide away from (switch_page).
      */
     animate: boolean;
     /** Transition direction: `true` when the new page comes from BELOW (pop/replace). */
     pop: boolean;
     /**
-     * Whether `visible-page-tag` re-notifies: switch_page:927-930 notifies only
+     * Whether `visible-page-tag` re-notifies: switch_page notifies only
      * when the outgoing OR the incoming page carries a tag.
      */
     tagNotify: boolean;
@@ -93,14 +93,14 @@ export type NavigationPagePropsResolver<P> = (page: P) => AdwNavigationPageProps
  * What a shortcut handler must do with the key event. `'stop'` is
  * `GDK_EVENT_STOP` — notably also returned WITHOUT popping when the visible page
  * has `can-pop = FALSE`, so the key is not forwarded to an enclosing navigation
- * view (pop_shortcut_cb:1150-1152).
+ * view (pop_shortcut_cb).
  */
 export type NavigationShortcutResult = 'stop' | 'propagate';
 /** Construction defaults + the diagnostic seam. */
 export interface NavigationViewOptions {
-    /** `AdwNavigationView:animate-transitions`, default `true` (init:2142). */
+    /** `AdwNavigationView:animate-transitions`, default `true` (init). */
     animateTransitions?: boolean;
-    /** `AdwNavigationView:pop-on-escape`, default `true` (init:2143). */
+    /** `AdwNavigationView:pop-on-escape`, default `true` (init). */
     popOnEscape?: boolean;
     /** Where rejected mutations are reported. Unset = silent. */
     onDiagnostic?: NavigationDiagnosticListener;
@@ -136,9 +136,9 @@ export declare class NavigationViewState<P = unknown> {
     get depth(): number;
     /** Every registered page (static + dynamically pushed), in registration order. */
     get pages(): readonly P[];
-    /** The top of the stack, or `null` when the stack is empty (get_visible_page:3165). */
+    /** The top of the stack, or `null` when the stack is empty (get_visible_page). */
     get visiblePage(): P | null;
-    /** The visible page's tag, or `null` — never `''` for an untagged page (get_visible_page_tag:3195). */
+    /** The visible page's tag, or `null` — never `''` for an untagged page (get_visible_page_tag). */
     get visiblePageTag(): string | null;
     /** Whether push/pop transitions animate. */
     get animateTransitions(): boolean;
@@ -161,89 +161,85 @@ export declare class NavigationViewState<P = unknown> {
     /** `page`'s `can-pop`. `true` for an unregistered page, matching the property default. */
     canPopOf(page: P): boolean;
     /**
-     * The page with this tag, or `null` (find_page:2774).
+     * The page with this tag, or `null` (find_page).
      *
      * Byte-exact: the C table is `g_str_hash`/`g_str_equal`, so NFC and NFD
      * spellings of the same word are DIFFERENT keys and `''` is a valid one.
      * Dynamically-pushed pages are found too — `maybe_add_page` routes through
-     * `add_page`, which indexes the tag (:1281-1282).
+     * `add_page`, which indexes the tag.
      */
     findPage(tag: string): P | null;
     /**
-     * The page popping `page` would reveal (get_previous_page:3228) — `null` when
+     * The page popping `page` would reveal (get_previous_page) — `null` when
      * `page` is the root page or is not on the stack.
      */
     getPreviousPage(page: P): P | null;
     /**
-     * Permanently add `page` (adw_navigation_view_add:2719). A page added this way
-     * survives being popped.
-     *
-     * Two rules that were missing from the renderers:
-     *   1. Adding a page that is on the stack as a DYNAMIC page converts it to a
-     *      permanent one and does nothing else (:2725-2730) — the stack does not
-     *      move and no change is emitted.
-     *   2. The auto-push fires whenever the stack is EMPTY, not only for the very
-     *      first page ever added (add_page:1284) — so `add()` after `replace([])`
-     *      pushes again.
+     * Permanently add `page` (`adw_navigation_view_add`); a page added this way survives
+     * being popped. Two easily-missed rules:
+     * 1. adding a page that is on the stack as a DYNAMIC page converts it to a permanent
+     * one and does nothing else — the stack does not move and nothing is emitted;
+     * 2. the auto-push fires whenever the stack is EMPTY, not only for the first page
+     * ever added, so `add()` after `replace([])` pushes again.
      *
      * Returns `false` (with a `duplicate-tag` diagnostic) when the tag collides.
      */
     add(page: P, props?: AdwNavigationPageProps): boolean;
     /**
-     * Remove `page` (adw_navigation_view_remove:2750 → remove_page:1312).
+     * Remove `page` (adw_navigation_view_remove → remove_page).
      *
      * If the page is on the stack the removal is DEFERRED: the page is marked
-     * remove-on-pop and destroyed when it is popped (:1323-1326). Otherwise it is
+     * remove-on-pop and destroyed when it is popped. Otherwise it is
      * unregistered immediately and its tag freed. Returns `false` only for a page
      * this view does not know.
      */
     remove(page: P): boolean;
     /**
-     * Set `page`'s tag (adw_navigation_page_set_tag:2437). Silent no-op when
-     * unchanged (:2448); rejected with `duplicate-tag` when another page already
-     * owns the tag, in which case the OLD tag is kept (:2456-2460).
+     * Set `page`'s tag (adw_navigation_page_set_tag). Silent no-op when
+     * unchanged; rejected with `duplicate-tag` when another page already
+     * owns the tag, in which case the OLD tag is kept.
      */
     setTag(page: P, tag: string | null): boolean;
     /**
-     * Set `page`'s title (adw_navigation_page_set_title:2508). Drives the header-bar
+     * Set `page`'s title (adw_navigation_page_set_title). Drives the header-bar
      * title and the NEXT page's back-button tooltip. `null`/`undefined` is rejected
-     * — the C has `g_return_if_fail (title != NULL)` (:2514).
+     * — the C has `g_return_if_fail (title != NULL)`.
      */
     setTitle(page: P, title: string): boolean;
     /**
-     * Set `page`'s `can-pop` (adw_navigation_page_set_can_pop:2569). Gates
+     * Set `page`'s `can-pop` (adw_navigation_page_set_can_pop). Gates
      * shortcuts, gestures and the back button — deliberately NOT {@link pop}.
      */
     setCanPop(page: P, canPop: boolean): boolean;
     /**
-     * Push `page` onto the stack (adw_navigation_view_push:2800).
+     * Push `page` onto the stack (adw_navigation_view_push).
      *
      * A page the view has never seen is registered as DYNAMIC (destroyed when
-     * popped, maybe_add_page:1307-1308); an already-registered one keeps its
-     * permanence, because maybe_add_page returns early for it (:1296-1297). That
+     * popped, maybe_add_page); an already-registered one keeps its
+     * permanence, because maybe_add_page returns early for it. That
      * asymmetry is why a static page survives a push/pop round trip.
      *
      * Returns `false` with `already-in-stack` when the page is already on the
-     * stack (push_to_stack:942-952), or with `duplicate-tag` when its tag collides.
+     * stack (push_to_stack), or with `duplicate-tag` when its tag collides.
      */
     push(page: P, props?: AdwNavigationPageProps): boolean;
     /**
-     * Push the page carrying `tag` (adw_navigation_view_push_by_tag:2829). An
+     * Push the page carrying `tag` (adw_navigation_view_push_by_tag). An
      * unknown tag is rejected with `tag-not-found` and changes nothing.
      */
     pushByTag(tag: string): boolean;
     /**
-     * Pop the visible page (adw_navigation_view_pop:2869). `false` when there is
+     * Pop the visible page (adw_navigation_view_pop). `false` when there is
      * no visible page or no page beneath it.
      *
      * Deliberately IGNORES `can-pop`: the C function contains no such test and the
      * property docs say so in as many words — "Manually calling
-     * [method@NavigationView.pop] […] will still work" (:2560-2561). Use
+     * [method@NavigationView.pop] […] will still work". Use
      * {@link popFromShortcut} for the gated path.
      */
     pop(): boolean;
     /**
-     * Pop until `page` is visible (adw_navigation_view_pop_to_page:2913) — ONE
+     * Pop until `page` is visible (adw_navigation_view_pop_to_page) — ONE
      * atomic splice, so ONE visible-page notification carrying every popped page,
      * not N sequential pops. Ignores `can-pop` on the pages it passes.
      *
@@ -252,18 +248,18 @@ export declare class NavigationViewState<P = unknown> {
      */
     popToPage(page: P): boolean;
     /**
-     * Pop until the page carrying `tag` is visible (adw_navigation_view_pop_to_tag:2958).
+     * Pop until the page carrying `tag` is visible (adw_navigation_view_pop_to_tag).
      * An unknown tag yields `tag-not-found`; a known but off-stack one yields
      * `not-in-stack`.
      */
     popToTag(tag: string): boolean;
     /**
-     * Replace the whole stack (adw_navigation_view_replace:3002). Never animates
-     * (:3075) and emits no `popped` — `::replaced` is its own signal.
+     * Replace the whole stack (adw_navigation_view_replace). Never animates
+     * and emits no `popped` — `::replaced` is its own signal.
      *
-     * `null` entries are skipped (:3021, :3052) and a page listed twice is
-     * rejected on its second occurrence (:3055-3059). Old DYNAMIC pages are
-     * destroyed only when they are absent from the new set (:3033-3034); that
+     * `null` entries are skipped and a page listed twice is
+     * rejected on its second occurrence. Old DYNAMIC pages are
+     * destroyed only when they are absent from the new set; that
      * guard is what makes replacing the stack with the tag of a pushed page work.
      * An empty array leaves no visible page.
      *
@@ -272,16 +268,14 @@ export declare class NavigationViewState<P = unknown> {
     replace(pages: readonly (P | null)[], props?: NavigationPagePropsResolver<P>): void;
     /**
      * Replace the stack with the pages carrying `tags`
-     * (adw_navigation_view_replace_with_tags:3124).
+     * (adw_navigation_view_replace_with_tags).
      *
-     * Every tag is resolved BEFORE any mutation; an unknown one reports
-     * `tag-not-found` and becomes a null slot {@link replace} then skips, rather
-     * than aborting the call. Resolving up front is exactly what the web port's
-     * `replace()` failed to do.
+     * Every tag is resolved BEFORE any mutation; an unknown one reports `tag-not-found`
+     * and becomes a null slot {@link replace} then skips, rather than aborting the call.
      */
     replaceWithTags(tags: readonly string[]): void;
     /**
-     * Report that the outgoing transition finished (transition_done_cb:1029-1075),
+     * Report that the outgoing transition finished (transition_done_cb),
      * and receive the pages the renderer must now destroy.
      *
      * This is the injected timing seam replacing `AdwAnimation`'s "done" callback.
@@ -289,52 +283,52 @@ export declare class NavigationViewState<P = unknown> {
      * is precisely what `adw_animation_skip` does in the C when `animate` is FALSE.
      * A page pushed back onto the stack before the transition finished survives,
      * because the C routes this through `adw_navigation_view_remove` and its
-     * on-the-stack check (:1042 → remove_page:1323).
+     * on-the-stack check (:1042 → remove_page).
      */
     finishTransition(): readonly P[];
     /**
      * Whether the automatic back button is shown — `get_previous_page(visible) !==
-     * null && can_pop(visible)` (adw-back-button.c update_page:84-108). This is the
+     * null && can_pop(visible)` (adw-back-button.c update_page). This is the
      * ONLY place `can-pop` decides whether a page can be left.
      */
     canGoBack(): boolean;
     /**
      * The back button's tooltip: the title of the page the button would reveal,
      * falling back to `fallback` only when that title is empty
-     * (adw-back-button.c query_tooltip:399-419). `null` when there is no back
+     * (adw-back-button.c query_tooltip). `null` when there is no back
      * button at all.
      */
     backButtonTooltip(fallback?: string): string | null;
     /**
      * The `can-pop`-aware pop behind Alt+Left and the back mouse button
-     * (pop_shortcut_cb:1142-1158).
+     * (pop_shortcut_cb).
      *
      * Returns `'stop'` WITHOUT popping when the visible page has `can-pop = FALSE`
      * — deliberately, so the key is not forwarded to an enclosing navigation view.
      */
     popFromShortcut(): NavigationShortcutResult;
-    /** Escape-to-pop: {@link popFromShortcut} gated on `pop-on-escape` (escape_shortcut_cb:1175-1182). */
+    /** Escape-to-pop: {@link popFromShortcut} gated on `pop-on-escape` (escape_shortcut_cb). */
     popFromEscape(): NavigationShortcutResult;
     private _diagnose;
     private _emit;
     private _emitChange;
-    /** `add_page` (:1263) — register, index the tag, and auto-push into an empty stack. */
+    /** `add_page` — register, index the tag, and auto-push into an empty stack. */
     private _addPage;
-    /** `maybe_add_page` (:1290) — register an unknown page as DYNAMIC; keep a known one as it is. */
+    /** `maybe_add_page` — register an unknown page as DYNAMIC; keep a known one as it is. */
     private _maybeAddPage;
-    /** `push_to_stack` (:933) — the append plus its already-in-stack guard. */
+    /** `push_to_stack` — the append plus its already-in-stack guard. */
     private _pushToStack;
-    /** `pop_from_stack` (:969) — one splice, one switch, then the per-page destroys. */
+    /** `pop_from_stack` — one splice, one switch, then the per-page destroys. */
     private _popFromStack;
     /**
-     * `switch_page` (:824), minus the rendering: flush a still-pending deferred
+     * `switch_page`, minus the rendering: flush a still-pending deferred
      * destroy, decide whether this transition animates, and queue the new one.
      */
     private _beginSwitch;
     /**
      * Settle the deferred destroy owed by the last pop — the shared body of
      * {@link finishTransition} and the mid-transition flush in {@link _beginSwitch}.
-     * Both go through `adw_navigation_view_remove` in the C (:1042 / :868), so both
+     * Both go through `adw_navigation_view_remove` in the C, so both
      * inherit `remove_page`'s on-the-stack check: a page pushed BACK before the
      * transition ended survives and is merely re-marked remove-on-pop.
      */

package/lib/types/popover.d.ts

@@ -1,37 +1,25 @@
 /**
- * Padding inside a popover's content box, in px — `popover > contents { padding: 8px }`
- * (_popovers.scss:14).
+ * Padding inside a popover's content box, in px — `popover > contents { padding: 8px }`.
  *
- * NOT what a MENU popover uses: `popover.menu > contents` re-declares
- * `padding: 0` and moves the inset onto the item box as `$menu_margin` (6px)
- * (_menus.scss:58-66) — two element selectors plus a class, so it wins over the
- * plain `popover > contents` above. Both numbers are real; which one applies is
- * decided by the `.menu` class, not by this constant. See {@link POPOVER_MENU_PADDING}.
+ * NOT what a MENU popover uses: `popover.menu > contents` re-declares `padding: 0` and
+ * moves the inset onto the item box as `$menu_margin` (6px) — two element selectors
+ * plus a class, so it wins over the plain `popover > contents`. Both numbers are real;
+ * the `.menu` class decides which applies. See {@link POPOVER_MENU_PADDING}.
  */
 export declare const POPOVER_PADDING = 8;
 /**
- * Padding around the item box of a MENU popover, in px — `$menu_margin`
- * (_common.scss:11), applied by `popover.menu > contents > … > stack > box`
- * (_menus.scss:61-64) after that same rule zeroes the contents padding.
- *
- * This is the number the three hand-rolled copies actually used (`--spacing-xs`,
- * 6px). They were not wrong about the inset — they were wrong about the radius,
- * and one of them about the shadow.
+ * Padding around the item box of a MENU popover, in px — `$menu_margin`, applied by
+ * `popover.menu > contents > … > stack > box` after that same rule zeroes the contents
+ * padding.
  */
 export declare const POPOVER_MENU_PADDING = 6;
 /**
  * Corner radius of a popover surface, in px — `$popover_radius`, defined as
- * `$menu_radius + 6` = `9 + 6` (_common.scss:10,13) and applied at
- * _popovers.scss:15.
- *
- * All three copies got this wrong: two used `--card-radius` (12px, `$card_radius`)
- * and one `--button-radius` (9px, `$button_radius`).
+ * `$menu_radius + 6` = `9 + 6`. Not `$card_radius` (12px) and not `$button_radius`
+ * (9px), the two values a hand-rolled popover reaches for.
  */
 export declare const POPOVER_RADIUS = 15;
-/**
- * Corner radius of a menu item row, in px — `$menu_radius` (_common.scss:10),
- * applied by `modelbutton` at _menus.scss:138.
- */
+/** Corner radius of a menu item row, in px — `$menu_radius`, applied by `modelbutton`. */
 export declare const POPOVER_ITEM_RADIUS = 9;
 /** Payload of a {@link PopoverState} change. */
 export interface PopoverStateChange {
@@ -47,18 +35,15 @@ export interface PopoverStateChange {
 /** Subscriber for {@link PopoverState} changes. */
 export type PopoverStateListener = (change: PopoverStateChange) => void;
 /**
- * The open/closed state of a popover, with the programmatic-vs-interactive
- * distinction the other core states carry ({@link ComboState}, {@link SpinState},
- * {@link SplitButtonState}): a renderer re-emits `notify::*` only for the
- * interactive changes, so an application calling `popup()` does not look like a
- * user click.
+ * The open/closed state of a popover, with the programmatic-vs-interactive distinction
+ * the other core states carry ({@link ComboState}, {@link SpinState},
+ * {@link SplitButtonState}): a renderer re-emits `notify::*` only for the interactive
+ * changes, so an application calling `popup()` does not look like a user click.
  *
- * NAMING: the state exposes a `open` GETTER, so the mutators cannot also be
- * called `open()`/`close()` — a class cannot carry both under one name. They
- * take GTK's own vocabulary instead ({@link popup} / {@link popdown}, after
- * `adw_split_button_popup()` / `..._popdown()`), which is also what the
- * `<adw-popover>` element exposes. `SplitButtonState` resolved the same clash
- * as `openMenu()`/`closeMenu()`.
+ * NAMING: an `open` GETTER means the mutators cannot also be `open()`/`close()`, so
+ * they take GTK's vocabulary ({@link popup} / {@link popdown}, after
+ * `adw_split_button_popup()` / `..._popdown()`) — which is what `<adw-popover>`
+ * exposes too.
  *
  * Idempotent: setting the current value again is a no-op and notifies nobody.
  */
@@ -78,9 +63,9 @@ export declare class PopoverState {
     /** The anchor was activated by the user; flips open/closed. Returns whether it changed. */
     toggle(): boolean;
     /**
-     * The user dismissed the popover — an outside click, or Escape. Distinct
-     * from {@link popdown} only in the `interactive` flag, which is the whole
-     * point: a dismissal is a gesture, a `popdown()` call is not.
+     * The user dismissed the popover — an outside click, or Escape. Distinct from
+     * {@link popdown} only in the `interactive` flag: a dismissal is a gesture, a
+     * `popdown()` call is not.
      */
     dismiss(): boolean;
 }
@@ -113,43 +98,31 @@ export interface PopoverKeyContext {
 }
 /** {@link resolvePopoverKey}'s answer. */
 export interface PopoverKeyResolution {
-    /** What to do. */
     action: PopoverKeyAction;
     /** Item index for `focus`/`activate`; `-1` for `close` and `none`. */
     index: number;
 }
 /**
- * Resolve a key press inside an open popover to a focus/activation move.
- *
- * This is the `(current ± 1 + n) % n` arithmetic `adw-menu-button` and
- * `adw-drop-down` each spelled out, reconciled. Where the two copies differed:
+ * Resolve a key press inside an open popover to a focus/activation move — the
+ * `(current ± 1 + n) % n` arithmetic, with three decisions a reader cannot see in it:
  *
- * - **`ArrowUp` from no focus.** BOTH copies computed `(-1 - 1 + n) % n`, which
- *   is `n - 2` — the second-to-LAST item. Reachable in the drop-down on every
- *   open with `enable-search`, since it focuses the search entry. Fixed here to
- *   `n - 1`: ArrowUp from nothing enters the list at the END, the convention the
- *   ARIA menu/listbox patterns describe and the mirror of ArrowDown → `0`.
- *   Not verifiable against GTK in this tree — see the caveat below.
- * - **`Enter`/`Space`.** The drop-down activated the focused item; the menu
- *   button had no case and leaned on the browser activating a focused `<button>`
- *   natively. Reported as `'activate'` for both: a renderer that calls
- *   `preventDefault()` and then `.click()` activates exactly once, where relying
- *   on the native path makes the behaviour depend on the item's tag.
- * - **`Home`/`End` with a search entry focused.** The drop-down stole them
- *   unconditionally, so Home could not move the caret to the start of the query
- *   the user was typing. `'none'` here while `hasSearch && currentIndex < 0`.
- * - The `+ n` in `(current + 1 + n) % n` is defensive only — for `current` in
- *   `[-1, n)` it is arithmetically identical to `(current + 1) % n`. Not a
- *   divergence, just two spellings.
+ * - **`ArrowUp` from no focus** goes to `n - 1`, not to `(-1 - 1 + n) % n` = `n - 2`.
+ *   Entering the list at the END is the ARIA menu/listbox convention and the mirror of
+ *   ArrowDown → `0`; the second-to-last item is what the naive modulo gives.
+ * - **`Enter`/`Space`** report `'activate'` rather than leaning on the browser
+ *   activating a focused `<button>` natively: a renderer that calls
+ *   `preventDefault()` then `.click()` activates exactly once, where the native path
+ *   makes the behaviour depend on the item's tag.
+ * - **`Home`/`End`** are `'none'` while `hasSearch && currentIndex < 0`, so Home moves
+ *   the caret to the start of the query the user is typing.
  *
  * NOT VERIFIABLE IN THIS TREE: `refs/gtk` is empty and libadwaita vendors no
- * `adw-popover.c`, so `GtkPopover`'s own `position` / `autohide` / `has-arrow`
- * semantics — and GTK's exact keynav from an unfocused list — cannot be read
- * from source here. The wrap arithmetic below is the reconciliation of our two
- * copies against the ARIA patterns, not a claim about GTK's C.
+ * `adw-popover.c`, so `GtkPopover`'s own `position`/`autohide`/`has-arrow` semantics
+ * and GTK's keynav from an unfocused list cannot be read from source. The wrap
+ * arithmetic is reconciled against the ARIA patterns, not a claim about GTK's C.
  *
- * `Tab` is deliberately unhandled (`'none'`): GTK popovers trap focus, and doing
- * that in the DOM is a renderer concern (`inert`, a focus sentinel) with no
- * portable arithmetic to share.
+ * `Tab` is deliberately unhandled (`'none'`): GTK popovers trap focus, and doing that
+ * in the DOM is a renderer concern (`inert`, a focus sentinel) with no portable
+ * arithmetic to share.
  */
 export declare function resolvePopoverKey(key: string, context: PopoverKeyContext): PopoverKeyResolution;