@fusion.dev/helix-docs 0.145.0 → 0.147.0

package/content/overlays.mdx

@@ -78,14 +78,16 @@ press `Escape` again.
 
 A modal overlay keeps `Tab` inside itself while it is open, and it returns focus
 to the element that opened it. `Dialog` does this, and so does `Drawer` unless
-you set `modal="false"`. The page behind a modal `Dialog` or `Drawer` does not
+you set `modal="false"`. Set `dismissible` on either to draw a close control in
+the corner by the title. The page behind a modal `Dialog` or `Drawer` does not
 scroll while it is open.
 
 Opening a `Popover` moves focus to the first control in its panel, or to the
 panel where it holds none, and closing it from inside gives focus back to the
-trigger. It does not trap focus unless you set `modal`, which keeps `Tab` in the
-panel until it closes. When focus moves out of its trigger and its panel, the
-popover closes.
+trigger, however it closes, setting `open` included. It does not trap focus
+unless you set `modal`, which keeps `Tab` in the panel until it closes and hides
+the rest of the page from screen readers meanwhile. When focus moves out of its
+trigger and its panel, the popover closes.
 
 Press F8 to move focus to the `Toast` stack, and press it again to go back.
 Set `hotkey` on the stack to use another key. The stack's name says which key
@@ -109,6 +111,11 @@ names it with `for`. A Helix trigger is described as soon as it has rendered.
 A plain element in your markup is described the first time a reader points at
 it or focuses it, so the link is never written into markup your server sent.
 Write `aria-describedby` yourself to have the link in the server's markup.
+In the `for` form, the tooltip itself is out of the accessibility tree while
+its bubble is down, so a reader meets its words once, as the description.
+The pointer can move onto a tooltip's bubble and the bubble stays, so a reader
+can read it under a magnifier. Set `hoverable="false"` to hide it once the
+pointer reaches it.
 
 ## Keep an overlay open
 
@@ -143,9 +150,16 @@ finished. Select on them to draw an entrance or an exit of your own.
 A touch or a pen swipes a `Drawer` toward the edge it came from, and a `Toast`
 message toward the end of the line. A swipe past halfway, or a quick one, closes
 it through the same cancelable request as its close control. A `Drawer` with
-`snap-points` comes to rest at the nearest point, such as half open. In a
+`snap-points` comes to rest at the nearest point, such as half open, and
+`:state(snapped)` holds while it rests short of the whole panel. Moving focus
+with `Tab` to a control past the edge of the window opens it the rest of the
+way, and `snapTo()` moves it from script. In a
 `Lightbox`, a swipe across the viewer shows the next or the previous item. A
-mouse never swipes, because dragging with a mouse selects text.
+mouse never swipes, because dragging with a mouse selects text. A `Lightbox`
+with `max-zoom` also zooms: pinch the item, or double click or double tap it,
+and drag it about once zoomed. It swipes only while the item is at its own
+size. With `controls` it also draws zoom-out and zoom-in controls, and once a
+reader stops zooming it says the new scale, such as "Zoomed to 150%".
 
 ## Choose an overlay
 

package/content/state-and-control.mdx

@@ -106,11 +106,13 @@ current value. The pair comes from the platform. A native input reflects its
 `value` *content attribute* to `defaultValue`, and it keeps a dirty flag. Once a
 user has typed, the flag stops the attribute from changing the value.
 
-**A form reset clears a `value` or `checked` you wrote in markup.** A native
-`<input value="Ada">` resets to `Ada`, and `<helix-input value="Ada">` resets to
-empty, because a Helix control resets to `default-value` and `default-checked`.
-Write the starting value of a form control as `default-value`, or
-`default-checked` for a checkbox or a switch.
+**A form reset returns to a `value` or `checked` you wrote in markup**, as it
+does on a native control: `<input value="Ada">` and `<helix-input value="Ada">`
+both reset to `Ada`. Where `default-value` or `default-checked` is written, the
+reset returns to that instead. The attribute is read at the reset, and a
+framework that sets `value` as a property writes no attribute, so write the
+starting value of a form control as `default-value`, or `default-checked` for a
+checkbox or a switch, when a reset has to return to it.
 
 ## State is published as a custom state