gesso-core 0.2.1 → 0.4.0

package/CHANGELOG.md

@@ -1,5 +1,126 @@
 # gesso-core
 
+## 0.4.0
+
+### Minor Changes
+
+- **`DoubleClick`, dispatched after a second Click on the same node.** The pointer
+  controller pairs Clicks on the same node within 500 ms and 4 px — the window the
+  editing and selection controllers already use for a word — and dispatches
+  `DoubleClick` after the second, as the DOM's `dblclick` follows its `click`. A
+  press that became a drag or was cancelled spends the pair.
+
+  `onDoubleClick` on any element; `fireEvent` gains `doubleClick` and
+  `contextMenu`.
+
+- **A menu opened at a point stays on the screen.** A context menu's point was a
+  top and a left and nothing more, so a menu asked for near the bottom or right
+  edge opened off the screen.
+
+  The layout engine gains `anchorPoint`, a point placed beside as an anchor of no
+  size would be — the same flip and clamp — and overlays a `point` option that
+  uses it. `Menu`'s `at` opens below and to the right of the point, and above or
+  to the left when there is no room.
+
+  Found by a spreadsheet's status bar, whose menu opened below the window.
+
+### Patch Changes
+
+- **An absolute box past its containing block keeps its explicit size.** With no
+  room left on an axis, the loose constraint an absolute child was measured under
+  came out `(0, 0)`, which reads as tight, and a box with an explicit width or
+  height was laid out at zero on that axis — where one pixel of room would have
+  left it whole.
+
+  An explicit size is the box's own, as in CSS; the block no longer caps it.
+
+- **The browser shells post OS file drops.** The `fileDrop` message, its shape and
+  the session that turns it into an ordinary drag have existed since drop targets
+  did, and nothing posted one: a zone accepting `gesso/files` could be written and
+  never reached.
+
+  `attachFileDrop` is the shell half, shared by `createApp`'s worker shell and
+  `createSyncApp`'s single-thread one because it is the same four DOM events
+  either way. It answers drags that carry files and no others, prevents the
+  default on every `dragover` (which is what tells a browser the drop is wanted)
+  and on `drop` (or the tab is replaced by the file), and reads the bytes before
+  posting the drop. The worker shell transfers the buffers rather than copying
+  them; a drop whose files cannot be read is reported as a leave, so no zone stays
+  lit waiting. `GessoRuntime.applyFileDrop` hands the message to the tree's drag
+  session.
+
+  The core half was wrong in a way no spec could have caught: `applyFileDrop` began
+  a drag with the files of `enter` and, on `drop`, only moved it, so a zone
+  received the payload the drag started with. A browser lets a page see the _types_
+  of dragged files and nothing else until they are let go, so that payload has
+  empty names and no bytes — every file dropped from a desktop would have arrived
+  unopenable. The spec that covered it sent the same files on both phases, which is
+  the one shape a browser never produces. It now sends what one does.
+
+## 0.3.0
+
+### Minor Changes
+
+- 025321a: **`fanOut`, for when every node wants its own slice.** One source, N things on
+  screen, each reading one part of it: a grid, a timeline, a log viewer all arrive
+  at this shape, and the natural spelling does not scale. A pipe per slice runs N
+  pipelines on every emission whatever changed, and RxJS removes an observer from a
+  Subject by scanning its list, so tearing down a window of N is quadratic.
+
+  `fanOut(source, read, { initial })` holds one subscription for the whole registry
+  and hands out a stable cell per key. Its `changed` hint is where a frame is won: a
+  source that knows which keys a patch touched reads only those. Ten thousand live
+  keys, measured against a pipe per key: mount 29.8 ms to 10.7 ms, teardown 9.7 ms
+  to 3.7 ms, and one key changing 2.2 ms to 0.1 ms.
+
+  Reach for it when N is large _and each emission touches few of them_. A source
+  that republishes its whole window on every scroll gets the cheaper mount and
+  teardown and nothing from `changed`, because every key really did change.
+
+  It compares by reference where `select` and `derive` compare by content, which is
+  the opposite default for the opposite reason: those run once per emission and this
+  runs once per live key per emission. And a registry that has grown past a couple
+  of thousand keys having released none of them says so once, because `release` is
+  the caller's and forgetting it is the one thing here that goes wrong silently.
+
+  **`tabStop`, which is `tabindex="-1"`.** Focusable, reachable by a press and by
+  `focus()`, skipped by the Tab cycle. `focusable` only ever answered "may this node
+  hold focus", which is the wrong question for a container: `UiFocusManager.settleScope`
+  blurred when a scope held nothing focusable, so a `Dialog` whose content is a
+  sentence handed the keyboard to nothing and could not be dismissed with Escape.
+  `settleScope` now falls back to the scope root before blurring, and `Dialog` sets
+  `focusable: true, tabStop: false` on its body. Both halves are needed and neither
+  is enough alone.
+
+  **`borders()`, a border per edge, as paint.** `borderWidth` is one number and
+  `borderColor` one colour, so a node could not have a heavy bottom edge and a
+  hairline top. A border here is paint-only and a decoration is already a coloured
+  rectangle in the node's own paint pass, so four edges are four draw instances and
+  no extra nodes. `DecorationBox` gains `right` and `bottom` to put them: any two of
+  near edge, size and far edge fix an axis, which is CSS's rule for an absolutely
+  positioned box, and the only one that can express a side edge spanning between two
+  horizontal ones.
+
+  **`menuBarStep`, a menu bar's keyboard, as a peer of `Menu`.** `Menu` traps focus,
+  which is right for a popup opened by a button and wrong for a bar: with focus in
+  the panel, ArrowLeft cannot reach the bar to move to the menu next door, and that
+  is most of what makes a bar a bar. A pure function, generic in the command type,
+  that returns null for a key it does not claim, so a bar can still be tabbed out of.
+
+### Patch Changes
+
+- 025321a: **A finger can scroll a surface on both of its axes.** `UiTouchScroller` picked one
+  axis per container from its flex direction, exactly as `UiWheelController` did
+  before it was fixed, and dropped the other. So a viewport whose content overflows
+  in both directions — a spreadsheet's, which is one `ScrollView` over content wider
+  and taller than itself — could not be dragged sideways at all.
+
+  Each axis is now asked separately whether the container has room, through a
+  `hasScrollRoom` the wheel and the touch paths share rather than write twice, so
+  the two cannot drift on which container takes a gesture. A fling coasts per axis
+  and each axis passes the threshold on its own, so a diagonal throw coasts on both
+  and a vertical one does not drift sideways by whatever the thumb happened to do.
+
 ## 0.2.1
 
 ## 0.2.0