@gjsify/adwaita-core 0.36.0 → 0.37.0

package/lib/types/conformance/banner.d.ts

@@ -4,70 +4,54 @@ export interface BannerDefaultVector {
     property: 'title' | 'button-label' | 'revealed' | 'use-markup' | 'button-style';
     /** The `GParamSpec` default. */
     value: string | boolean;
-    /** Why this row exists — the rule or edge case it pins down. */
     rule: string;
 }
 /**
- * The five `GParamSpec` defaults (adw-banner.c:391-459).
- *
- * `revealed: false` and `useMarkup: true` are the two that were wrong in the
- * ports. `@gjsify/adwaita-nativescript` initialised `_revealed = true` and its
- * constructor never wrote `visibility`, so a banner showed itself on a device
- * and stayed hidden in the browser; both ports made `use-markup` opt-in, and the
- * browser element's comment claimed that WAS the C default.
+ * The five `GParamSpec` defaults. `revealed: false` and `use-markup: true` were wrong
+ * in both ports in opposite directions — a banner showed itself on a device and stayed
+ * hidden in the browser.
  */
 export declare const BANNER_DEFAULT_VECTORS: ReadonlyArray<BannerDefaultVector>;
 /** One button-visibility expectation. */
 export interface BannerButtonVisibleVector {
     /** The `button-label` value, or `null` for the `NULL` the C setter accepts. */
     label: string | null;
-    /** Whether `gtk_widget_set_visible` is handed a true value (:663). */
+    /** Whether `gtk_widget_set_visible` is handed a true value. */
     visible: boolean;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `adw_banner_set_button_label` (:663) — `gtk_widget_set_visible (button, label
- * && label[0])`.
- *
- * A FIRST-CHARACTER test. The whitespace rows are the ones that matter: a
- * renderer that trimmed before testing would hide a button GTK draws.
+ * `adw_banner_set_button_label` — `gtk_widget_set_visible (button, label && label[0])`,
+ * a FIRST-CHARACTER test. The whitespace rows are the ones that matter: a renderer that
+ * trimmed before testing would hide a button GTK draws.
  */
 export declare const BANNER_BUTTON_VISIBLE_VECTORS: ReadonlyArray<BannerButtonVisibleVector>;
 /** One button-label text expectation. */
 export interface BannerButtonTextVector {
-    /** The `button-label` value. */
     label: string;
     /** What a renderer without an accelerator layer paints. */
     text: string;
-    /** Why this row exists. */
     rule: string;
 }
 /**
  * The banner button's text after mnemonic resolution.
  *
- * The template pins the BUTTON to `use-underline=True` (adw-banner.ui:33) with
- * no property to turn it off, and pins the TITLE label to `use-underline=False`
- * (adw-banner.ui:20). So the same underscore is an accelerator marker in the
- * button and a literal in the title — which is why there is no title
- * counterpart to this table. Neither port stripped anything.
+ * The template pins the BUTTON to `use-underline=True` with no property to turn it off
+ * and the TITLE label to `use-underline=False`, so the same underscore is an
+ * accelerator marker in the button and a literal in the title — hence no title
+ * counterpart to this table.
  */
 export declare const BANNER_BUTTON_TEXT_VECTORS: ReadonlyArray<BannerButtonTextVector>;
 /** One `button-style` → style-class expectation. */
 export interface BannerButtonStyleVector {
     /** The `AdwBannerButtonStyle` nick. */
     style: 'default' | 'suggested';
-    /** The classes on the button node (:764-774). */
     classes: readonly string[];
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `adw_banner_set_button_style`'s switch (:764-774) — the property adds or
- * removes exactly one class and touches nothing else.
- *
- * Present in this vendored source since 1.7 (:34) and in NEITHER renderer, so a
- * banner asking for a suggested action button got a grey one in both.
+ * `adw_banner_set_button_style`'s switch (Since 1.7) — the property adds or removes
+ * exactly one class and touches nothing else.
  */
 export declare const BANNER_BUTTON_STYLE_VECTORS: ReadonlyArray<BannerButtonStyleVector>;
 /** One `button-style` attribute-parsing expectation. */
@@ -76,16 +60,12 @@ export interface BannerButtonStyleParseVector {
     input: string | null;
     /** The `AdwBannerButtonStyle` it resolves to. */
     style: 'default' | 'suggested';
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * Turning a renderer-supplied STRING into the enum.
- *
- * Not a C behaviour and cannot be: `adw_banner_set_button_style` range-guards an
- * `AdwBannerButtonStyle` it has already been handed (:756-757), so an
- * unrepresentable string never reaches it. Falling back to the property default
- * is what `g_object_set` does with an invalid nick, and it is the only answer
- * that keeps the two renderers agreeing on the same markup.
+ * Turning a renderer-supplied STRING into the enum. Not a C behaviour and cannot be:
+ * `adw_banner_set_button_style` range-guards an `AdwBannerButtonStyle` it has already
+ * been handed, so an unrepresentable string never reaches it. Falling back to the
+ * property default is what `g_object_set` does with an invalid nick.
  */
 export declare const BANNER_BUTTON_STYLE_PARSE_VECTORS: ReadonlyArray<BannerButtonStyleParseVector>;

package/lib/types/conformance/button-content.d.ts

@@ -4,87 +4,69 @@ export interface ButtonContentDefaultVector {
     property: 'icon-name' | 'label' | 'use-underline' | 'can-shrink';
     /** The `GParamSpec` default. */
     value: string | boolean;
-    /** Why this row exists. */
     rule: string;
 }
-/** The four `GParamSpec` defaults (adw-button-content.c:229-272). */
+/** The four `GParamSpec` defaults. */
 export declare const BUTTON_CONTENT_DEFAULT_VECTORS: ReadonlyArray<ButtonContentDefaultVector>;
 /** One icon-name resolution expectation. */
 export interface ButtonContentIconVector {
-    /** The `icon-name` value. */
     iconName: string;
-    /** The name the `GtkImage` is actually set from (:355-358). */
+    /** The name the `GtkImage` is actually set from. */
     resolved: string;
     /** Whether the resolved name is the empty-slot fallback rather than an app value. */
     isFallback: boolean;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `adw_button_content_set_icon_name` (:355-358).
+ * `adw_button_content_set_icon_name`.
  *
- * THE DOCS AND THE CODE DISAGREE AND THIS TABLE FOLLOWS THE CODE. Both doc
- * comments say an empty `icon-name` means the icon "is not shown" (:228 on the
- * property, :343 on the setter). Nothing in the widget hides it:
- * `gtk_widget_set_visible` is called on the LABEL only (:300, :398), `init` sets
- * the image to `image-missing` while `icon_name` is still `""` (:284, :294), and
- * the setter re-applies that fallback for every empty value (:355-356). So a
- * default-constructed `AdwButtonContent` draws the broken-image glyph, and both
- * ports — which followed the prose and hid the icon — are the ones that diverge.
- * Encoding the prose would have pinned their guess under the word "conformance".
+ * The upstream docs and the code disagree and this table follows the CODE: both doc
+ * comments say an empty `icon-name` means the icon "is not shown", but nothing in the
+ * widget hides it — `gtk_widget_set_visible` is called on the LABEL only, `init` sets
+ * the image to `image-missing` while `icon_name` is still `""`, and the setter
+ * re-applies that fallback for every empty value. A default-constructed
+ * `AdwButtonContent` therefore draws the broken-image glyph.
  */
 export declare const BUTTON_CONTENT_ICON_VECTORS: ReadonlyArray<ButtonContentIconVector>;
 /** One label-slot expectation. */
 export interface ButtonContentLabelVector {
-    /** The `label` value. */
     label: string;
-    /** Whether the label node is in the tree (:398). */
+    /** Whether the label node is in the tree. */
     visible: boolean;
-    /** Whether the icon takes the box's free space (:399). */
+    /** Whether the icon takes the box's free space. */
     iconExpands: boolean;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `adw_button_content_set_label` (:398-399) — the two calls it makes, both keyed
+ * `adw_button_content_set_label` — the two calls it makes, both keyed
  * on `label[0]` and therefore exact complements.
  */
 export declare const BUTTON_CONTENT_LABEL_VECTORS: ReadonlyArray<ButtonContentLabelVector>;
 /** One label-text expectation. */
 export interface ButtonContentTextVector {
-    /** The `label` value. */
     label: string;
-    /** The `use-underline` value. */
     useUnderline: boolean;
     /** What a renderer without an accelerator layer paints. */
     text: string;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `adw_button_content_set_use_underline` (:442) applied to the label.
- *
- * Absent from both ports, and it is the property the class docs single out —
- * "handles … connecting the mnemonic to the button automatically" (:42-43). The
- * default is FALSE (:253-256), so an underscore in an unconfigured button
- * content is a LITERAL, unlike the banner's action button.
+ * `adw_button_content_set_use_underline` applied to the label — the property the class
+ * docs single out ("handles … connecting the mnemonic to the button automatically").
+ * The default is FALSE, so an underscore in an unconfigured button content is a
+ * LITERAL, unlike the banner's action button.
  */
 export declare const BUTTON_CONTENT_TEXT_VECTORS: ReadonlyArray<ButtonContentTextVector>;
 /** One `can-shrink` expectation. */
 export interface ButtonContentEllipsizeVector {
-    /** The `can-shrink` value. */
     canShrink: boolean;
-    /** The label's `PangoEllipsizeMode` (:489-491). */
+    /** The label's `PangoEllipsizeMode`. */
     ellipsize: 'none' | 'end';
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `adw_button_content_set_can_shrink` (:489-491), which the getter reads back as
- * `ellipsize != PANGO_ELLIPSIZE_NONE` (:462).
- *
- * The browser port had this; the NativeScript port had no such property, so the
- * shared story's `canShrink` control did nothing there.
+ * `adw_button_content_set_can_shrink`, which the getter reads back as
+ * `ellipsize != PANGO_ELLIPSIZE_NONE`.
  */
 export declare const BUTTON_CONTENT_ELLIPSIZE_VECTORS: ReadonlyArray<ButtonContentEllipsizeVector>;
 /** One style-class targeting expectation. */
@@ -93,18 +75,14 @@ export interface ButtonContentStyleTargetVector {
     ancestors: ReadonlyArray<'button' | 'menu-button' | 'split-button' | 'other'>;
     /** Index into {@link ancestors} that receives `image-text-button`, or `null`. */
     target: number | null;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `adw_button_content_root` (:108-116) — nearest `GtkButton`, then ONE
- * substitution: if that button's DIRECT parent is an `AdwSplitButton`, the class
- * moves to the split button (:112-113).
+ * `adw_button_content_root` — nearest `GtkButton`, then ONE substitution: if that
+ * button's DIRECT parent is an `AdwSplitButton`, the class moves to the split button.
  *
- * Neither renderer applied the class to anything at all, so every row here is a
- * new assertion rather than a pinned behaviour. The split-button row is the one
- * with a CSS consequence beyond padding: the class on the `splitbutton` node
- * selects `splitbutton.image-text-button > button` (_buttons.scss:499-507),
- * which is a different declaration block from the plain-button one.
+ * The split-button row is the one with a CSS consequence beyond padding: the class on
+ * the `splitbutton` node selects `splitbutton.image-text-button > button`, a different
+ * declaration block from the plain-button one.
  */
 export declare const BUTTON_CONTENT_STYLE_TARGET_VECTORS: ReadonlyArray<ButtonContentStyleTargetVector>;

package/lib/types/conformance/carousel.d.ts

@@ -5,10 +5,11 @@ export interface CarouselSnapPointVector {
     sizes: readonly number[];
     /** `snapPoint[i] = (Σ_{j≤i} size[j]) − 1`. */
     snapPoints: readonly number[];
-    /** Why this row exists. */
     rule: string;
 }
-/** `adw_carousel_size_allocate`'s accumulation (adw-carousel.c:777-789).  *
+/**
+ * `adw_carousel_size_allocate`'s accumulation.
+ *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (CAROUSEL_PAGE_LIST_VECTORS)
  */
 export declare const CAROUSEL_SNAP_POINT_VECTORS: ReadonlyArray<CarouselSnapPointVector>;
@@ -18,82 +19,72 @@ export interface CarouselSizesFromSnapPointsVector {
     snapPoints: readonly number[];
     /** `sizes[0] = points[0] + 1`, `sizes[i] = points[i] − points[i−1]`. */
     sizes: readonly number[];
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * The inverse both indicators reconstruct sizes with
- * (adw-carousel-indicator-dots.c:189-191, :248-250) — the only channel through
- * which an indicator can learn per-page reveal state.
+ * The inverse both indicators reconstruct sizes with — the only channel through which an
+ * indicator can learn per-page reveal state.
  *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (CAROUSEL_PAGE_LIST_VECTORS)
  */
 export declare const CAROUSEL_SIZES_FROM_SNAP_POINTS_VECTORS: ReadonlyArray<CarouselSizesFromSnapPointsVector>;
 /** One `carouselRange` expectation. */
 export interface CarouselRangeVector {
-    /** The snap points the range is derived from. */
     snapPoints: readonly number[];
-    /** Pending `position_shift`, which C folds into the bound (:219). */
+    /** Pending `position_shift`, which C folds into the bound. */
     positionShift: number;
     /** Always 0. */
     lower: number;
     /** `MAX (0, positionShift + last snap point)`. */
     upper: number;
-    /** Why this row exists. */
     rule: string;
 }
-/** `get_range` (adw-carousel.c:207-220).  *
+/**
+ * `get_range`.
+ *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (CAROUSEL_PAGE_LIST_VECTORS)
  */
 export declare const CAROUSEL_RANGE_VECTORS: ReadonlyArray<CarouselRangeVector>;
 /** One `carouselClampPosition` expectation. */
 export interface CarouselClampVector {
-    /** The proposed position. */
     position: number;
-    /** The snap points defining the range. */
     snapPoints: readonly number[];
     /** `CLAMP (position, lower, upper)`. */
     clamped: number;
-    /** Why this row exists. */
     rule: string;
 }
-/** `set_position`'s guard (adw-carousel.c:269).  *
+/**
+ * `set_position`'s guard.
+ *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (CAROUSEL_PAGE_LIST_VECTORS)
  */
 export declare const CAROUSEL_CLAMP_VECTORS: ReadonlyArray<CarouselClampVector>;
 /** One `carouselPageAtPosition` expectation. */
 export interface CarouselPageAtPositionVector {
-    /** The scroll position to resolve. */
     position: number;
     /** The snap points of the pages that count. */
     snapPoints: readonly number[];
     /** The page index, `-1` when there are no pages. */
     page: number;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `get_page_at_position` → `get_closest_child_at` (adw-carousel.c:222-239,
- * :180-205). The `.5` rows are the regression pins: C's comparison is a strict
+ * `get_page_at_position` → `get_closest_child_at` . The `.5` rows are the regression pins: C's comparison is a strict
  * `>`, so an equidistant LATER page never replaces the earlier one, while both
  * ports used `Math.round`, which rounds .5 up.
  */
 export declare const CAROUSEL_PAGE_AT_POSITION_VECTORS: ReadonlyArray<CarouselPageAtPositionVector>;
 /** One `carouselNavigateTarget` expectation. */
 export interface CarouselNavigateVector {
-    /** Current scroll position. */
     position: number;
-    /** Number of pages. */
     nPages: number;
-    /** Which way the key moves. */
     direction: CarouselDirection;
     /** The target page, `null` when C returns FALSE. */
     target: number | null;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `navigate_to_direction` (adw-carousel.c:475-508).
+ * `navigate_to_direction`.
  *
  * The rounding here is C's `round()` — half AWAY FROM ZERO — and it is
  * deliberately not the half-down tie-break of
@@ -104,21 +95,19 @@ export interface CarouselNavigateVector {
 export declare const CAROUSEL_NAVIGATE_VECTORS: ReadonlyArray<CarouselNavigateVector>;
 /** One `carouselWheelStep` expectation. */
 export interface CarouselWheelVector {
-    /** Horizontal delta. */
     deltaX: number;
-    /** Vertical delta. */
     deltaY: number;
-    /** The carousel's orientation. */
     orientation: CarouselOrientation;
     /** The `GdkInputSource` class of the event. */
     source: CarouselScrollSource;
     /** Pages to step; `0` means the event propagates. */
     step: -1 | 0 | 1;
-    /** Why this row exists. */
     rule: string;
 }
-/** `scroll_cb`'s axis/source rules (adw-carousel.c:537-559).  *
- * CORE-ONLY: GAP — the browser carousel handles `wheel` without routing it through `resolveCarouselWheel`, and the NativeScript one has no wheel at all. Tracked in #1072
+/**
+ * `scroll_cb`'s axis/source rules.
+ *
+ * CORE-ONLY: GAP — the browser carousel routes `wheel` through `CarouselState.handleWheel` but publishes no per-notch answer to assert, and the NativeScript one has no wheel at all. Tracked in #1072
  */
 export declare const CAROUSEL_WHEEL_VECTORS: ReadonlyArray<CarouselWheelVector>;
 /** One step of a wheel-lockout script. */
@@ -129,7 +118,6 @@ export interface CarouselWheelLockoutStep {
     deltaY: number;
     /** What `handleWheel` must return. */
     step: -1 | 0 | 1;
-    /** The position afterwards. */
     position: number;
 }
 /** One end-to-end wheel-lockout expectation. */
@@ -138,17 +126,14 @@ export interface CarouselWheelLockoutVector {
     pages: number;
     /** The events, in order, each with the clock reading it arrives at. */
     steps: readonly CarouselWheelLockoutStep[];
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * `SCROLL_TIMEOUT_DURATION` (adw-carousel.c:22) and the `scroll_timeout_id` gate
- * (:526, :571-574) — a wheel notch arms a 150 ms lockout during which further
- * notches propagate instead of paging.
+ * `SCROLL_TIMEOUT_DURATION` and the `scroll_timeout_id` gate — a wheel notch arms a 150 ms
+ * lockout during which further notches propagate instead of paging.
  *
- * The web port replaced this with a non-decaying delta accumulator, so +30 then
- * −30 cancelled out where libadwaita pages twice, and a slow wheel never
- * reached the threshold at all.
+ * A non-decaying delta accumulator is the wrong shape for this: +30 then −30 cancels out
+ * where libadwaita pages twice, and a slow wheel never reaches the threshold at all.
  *
  * CORE-ONLY: GAP — the lockout is a real elapsed-time rule and neither element has a clock seam to drive it with. Tracked in #1072
  */
@@ -157,28 +142,25 @@ export declare const CAROUSEL_WHEEL_LOCKOUT_VECTORS: ReadonlyArray<CarouselWheel
 export interface CarouselReorderShiftVector {
     /** Snap point of the page the carousel is closest to. */
     closestPoint: number;
-    /** Snap point the moved page had. */
     oldPoint: number;
-    /** Snap point it lands on. */
     newPoint: number;
-    /** The moved page's reveal size. */
     size: number;
     /** How far `position` must move so the visible page does not jump. */
     shift: number;
-    /** Why this row exists. */
     rule: string;
 }
-/** The three branches of `adw_carousel_reorder`'s compensation (adw-carousel.c:1488-1495).  *
+/**
+ * The three branches of `adw_carousel_reorder`'s compensation.
+ *
  * CORE-ONLY: an internal step of a pipeline whose COMPOSED result is renderer-driven — driving it separately would assert the same thing twice (CAROUSEL_PAGE_LIST_VECTORS)
  */
 export declare const CAROUSEL_REORDER_SHIFT_VECTORS: ReadonlyArray<CarouselReorderShiftVector>;
 /**
  * One operation in a page-list script.
  *
- * `insert` and `remove` mean "and finish the reveal immediately", which is what
- * a carousel with the default `reveal-duration` of 0 (adw-carousel.c:1206) does
- * and what both renderers' page APIs do. The mid-animation states are pinned
- * separately by {@link CAROUSEL_REVEAL_VECTORS}.
+ * `insert` and `remove` mean "and finish the reveal immediately", which is what a carousel
+ * with the default `reveal-duration` of 0 does and what both renderers' page APIs do. The
+ * mid-animation states are pinned separately by {@link CAROUSEL_REVEAL_VECTORS}.
  */
 export type CarouselPageOp = {
     readonly kind: 'insert';
@@ -208,9 +190,7 @@ export interface CarouselStateSnapshot {
     nPages: number;
     /** Reveal sizes of every TRACKED child, including ones being removed. */
     sizes: readonly number[];
-    /** Snap points of every tracked child. */
     snapPoints: readonly number[];
-    /** The clamped fractional position. */
     position: number;
     /** The current page index, `-1` when empty. */
     page: number;
@@ -219,24 +199,17 @@ export interface CarouselStateSnapshot {
 export interface CarouselPageListVector {
     /** Pages the carousel starts with, all settled at size 1. */
     pages: readonly string[];
-    /** The script, applied in order. */
     ops: readonly CarouselPageOp[];
     /** What each op returned (`settle` reports `true`). */
     opResults: readonly boolean[];
     /** The `page-changed` indices emitted while the script ran, in order. */
     pageChanged: readonly number[];
-    /** The state afterwards. */
     expected: CarouselStateSnapshot;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * Insert / remove / reorder ordering and the position compensation, on a
- * carousel whose reveals complete instantly — the shape both renderers expose.
- *
- * The whole family is new to both ports: the web port snapshotted its children
- * once in `connectedCallback` and never looked again, and the NS port had
- * `addPage` and nothing else.
+ * Insert / remove / reorder ordering and the position compensation, on a carousel whose
+ * reveals complete instantly — the shape both renderers expose.
  */
 export declare const CAROUSEL_PAGE_LIST_VECTORS: ReadonlyArray<CarouselPageListVector>;
 /** One operation in a reveal script — the mid-animation half of the state machine. */
@@ -262,37 +235,24 @@ export type CarouselRevealOp = {
 export interface CarouselRevealVector {
     /** Pages the carousel starts with, all settled at size 1. */
     pages: readonly string[];
-    /** The script, applied in order. */
     ops: readonly CarouselRevealOp[];
-    /** The state afterwards. */
     expected: CarouselStateSnapshot;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * The reveal lifecycle: a page enters at size 0 and grows, leaves `n-pages`
- * before its geometry, and drags the position along whenever it sits at or
- * before the page on screen.
- *
- * Neither port has any of this — both treat the page list as fixed — so every
- * row is new behaviour rather than a regression pin.
+ * The reveal lifecycle: a page enters at size 0 and grows, leaves `n-pages` before its
+ * geometry, and drags the position along whenever it sits at or before the page on screen.
  */
 export declare const CAROUSEL_REVEAL_VECTORS: ReadonlyArray<CarouselRevealVector>;
 /** One property-default expectation. */
 export interface CarouselPropertyDefaultVector {
-    /** The `CarouselState` accessor. */
     property: 'orientation' | 'interactive' | 'allowScrollWheel' | 'allowLongSwipes' | 'spacing' | 'revealDuration';
-    /** What a freshly constructed carousel reports. */
     value: string | number | boolean;
-    /** Why this row exists. */
     rule: string;
 }
 /**
- * The `AdwCarousel` property defaults. Two of them are regression pins:
- * `allow-scroll-wheel` is TRUE, which the web port inverted by reading a bare
- * attribute presence (so a plain `<adw-carousel>` ignored the wheel entirely
- * while its own header comment claimed the opposite), and `allow-long-swipes` is
- * FALSE, which the web port carried as a property whose two ternary branches
- * were identical.
+ * The `AdwCarousel` property defaults. Two are regression pins: `allow-scroll-wheel` is
+ * TRUE, which a bare attribute-presence read inverts (a plain `<adw-carousel>` then ignores
+ * the wheel entirely), and `allow-long-swipes` is FALSE.
  */
 export declare const CAROUSEL_PROPERTY_DEFAULT_VECTORS: ReadonlyArray<CarouselPropertyDefaultVector>;

package/lib/types/conformance/checks.d.ts

@@ -7,22 +7,18 @@ export interface RadioGroupStep {
     op: 'select';
     /** The group name — what `name` scopes in HTML, and what the state keys on. */
     name: string;
-    /** The member's value. */
     value: string;
 }
 /** One radio-group scenario. */
 export interface RadioGroupVector {
-    /** Short scenario name. */
     name: string;
     /** The members that exist, as `[group, value]` pairs — what the renderer mounts. */
     members: ReadonlyArray<readonly [string, string]>;
-    /** The mutations, applied in order to a fresh state. */
     steps: readonly RadioGroupStep[];
     /** `selected(group)` afterwards, one entry per group in {@link members}. */
     selected: ReadonlyArray<readonly [string, string | null]>;
     /** Every change the state emits, in order. This IS the renderer's repaint feed. */
     emitted: ReadonlyArray<RadioGroupChange>;
-    /** Why this row exists — the rule or edge case it pins down. */
     rule: string;
 }
 /** `RadioGroupState.select` and the exclusivity it publishes. */