leesto-connect 0.6.0 → 0.8.0

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/README.md CHANGED
@@ -27,7 +27,7 @@ sessions** of your pages.
27
27
  release needs a new tag. unpkg resolves the range by redirecting to the exact
28
28
  version, so the entry and its lazy chunks always come from the same build
29
29
  (avoid CDNs that serve ranges without redirecting). To freeze a build instead,
30
- pin it exactly: `https://unpkg.com/leesto-connect@0.6.0/dist/leesto-connect.js`.
30
+ pin it exactly: `https://unpkg.com/leesto-connect@0.8.0/dist/leesto-connect.js`.
31
31
 
32
32
  Options via data attributes:
33
33
 
@@ -44,6 +44,17 @@ and submits it with the test account chosen in the Lab. It never touches sign-up
44
44
  password-reset, magic-link or newsletter forms, never logs credentials, and does
45
45
  nothing outside an authorised Leesto shell. No configuration on your side.
46
46
 
47
+ The `login-anchor` capability: when the Lab asks for it (`leesto:login-watch`
48
+ with `anchor: true`), the connector reports the position of the login field
49
+ (`leesto:login-anchor`, a rectangle, never its value) and signals the tester's
50
+ clicks and typing (`leesto:login-interaction`). It also tells the Lab when the
51
+ tester enters the login field (`leesto:login-field-focus`, never a focus set by
52
+ the page itself) and presses ↓ or Escape there (`leesto:login-field-key`), so the Lab
53
+ can open its account list like browser autofill. When that list closes, the Lab
54
+ may ask the connector to put the focus back in the field
55
+ (`leesto:login-focus-field`). The Lab draws its sign-in button and list on top;
56
+ nothing is added to your page.
57
+
47
58
  ## Install (React / bundled app)
48
59
 
49
60
  If your app bundles its own dependencies, import the package once in your client
@@ -72,6 +83,17 @@ markers always apply and no setting can lift them:
72
83
  (placeholder only).
73
84
  - `.leesto-mask-text` / `[data-private]` — structure kept, text masked.
74
85
 
86
+ At every level, links and image addresses in the replay (`href`, `src`,
87
+ `srcset`, `url()` in `style`…) are cut to origin and path, `mailto:` / `tel:`
88
+ links to their scheme, and emails or card numbers are removed from `data-*`
89
+ attributes.
90
+
91
+ Screenshots are taken by the tester, who sees them before sending. They keep
92
+ the page text readable, whatever the level, but always mask field values and
93
+ the text of `.leesto-mask-text` / `[data-private]`; `.leesto-mask` /
94
+ `[data-leesto-block]` areas are covered, and an element inside one of them is
95
+ never captured on its own.
96
+
75
97
  Console and network diagnostics are redacted separately (emails, card numbers,
76
98
  tokens in URLs).
77
99