@botiverse/porthole 0.14.2 → 0.14.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,22 @@
4
4
  section); the reasons for every change are in [docs/DECISIONS.md](docs/DECISIONS.md), by the
5
5
  P-numbers below.
6
6
 
7
+ ## 0.14.3
8
+
9
+ - **Changed (P119, part of porthole#42):** on touch, an annotation marker takes a tap anywhere in a
10
+ box of at least 44 by 44 CSS px centred on its bubble, so a finger a few px off still opens it.
11
+ The bubble looks the same. Where two such boxes overlap, the marker whose bubble's centre is
12
+ nearest takes the tap. A press there goes the way one on the bubble does (stopped in the shell's
13
+ layer, a trusted click, `activated` with the bubble's box). The boxes are there while the last
14
+ pointer was a finger or a pen (before any, where `(any-pointer: coarse)` matches); a mouse's
15
+ move takes them away, so a mouse is as before, also on a touch laptop. Trade-off: on touch, a
16
+ tap within 13 px of a bubble is the marker's, not the words' under it.
17
+ - **Tests (P119):** `test/annotate.test.ts` (the hit rule); `leak/annotate.spec.ts` on all three
18
+ engines: taps 11 px off a bubble after the page scrolled itself, the nearest of two, a tap past
19
+ the box reaching the page, a marker pinned at the frame's top clicked and tapped where it is
20
+ drawn, and a mouse just off a bubble reaching the page. Raft QA's two reports (a tap after an
21
+ in-page `scrollBy`, a pinned marker's click) did not reproduce in the shell (DECISIONS P119).
22
+
7
23
  ## 0.14.2
8
24
 
9
25
  - **New (React, P118):** `PortholeFrame` and `PortholeView` take `trackedAnnotation` (a shown