@underlayerdev/ui 0.8.0 → 0.8.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@underlayerdev/ui",
-  "version": "0.8.0",
+  "version": "0.8.2",
   "peerDependencies": {
     "@angular/cdk": "^22.0.0",
     "@angular/common": "^22.0.0",

package/types/underlayerdev-ui.d.ts

@@ -1611,15 +1611,17 @@ declare class SelectableRowComponent {
     private justLongPressed;
     constructor();
     /**
-     * Once every row shows a checkbox in place of its media (compact +
-     * selecting), the checkbox is the only thing with its own toggle handler
-     * — everything else in the row (the content slot, empty space) does
-     * nothing on tap, which defeats the point of showing a large, easy-to-hit
-     * target. Toggling on any tap in that state fixes it; it's safe to do
-     * unconditionally (regardless of what's projected) because a consumer
-     * whose content contains a routerLink is already expected to have nulled
-     * that binding out while `selectionActive` — so there's no competing
-     * navigation to accidentally trigger.
+     * While selecting, a tap anywhere in the row toggles it — not just on the
+     * checkbox. This applies on every device, not only once the checkbox has
+     * replaced the media (compact): otherwise the row's content on
+     * fine-pointer devices would only be togglable by precisely hitting the
+     * small hover-revealed checkbox, which is inconsistent with how compact
+     * mode behaves and isn't how Gmail/Photos-style bulk-select works even on
+     * desktop web. It's safe to do unconditionally (regardless of what's
+     * projected) because a consumer whose content contains a routerLink is
+     * already expected to have nulled that binding out while
+     * `selectionActive` — so there's no competing navigation to accidentally
+     * trigger.
      */
     onHostClick(event: MouseEvent): void;
     static ɵfac: _angular_core.ɵɵFactoryDeclaration<SelectableRowComponent, never>;