@updog/data-editor-wc 0.1.64 → 0.1.66

package/README.md

@@ -120,6 +120,20 @@ Use for primitive values. The element observes these and re-renders on change.
 
 Everything else — objects, functions, arrays — must be set as a JS property or via `configure()`.
 
+**Never put a callback in a template.** Set `onComplete`, `onError`, `onColumnMatch` and `onValueMatch`
+through `configure()` or a property assignment. Written as a template binding they silently do nothing in
+Vue and Svelte, and break the build in Angular.
+
+```html
+<!-- wrong -->
+<updog-editor :onComplete="save" />
+```
+
+```js
+// right
+editor.configure({ onComplete: save });
+```
+
 ```js
 const editor = document.querySelector("updog-editor");
 editor.columns = [...];
@@ -484,9 +498,13 @@ See the [Styling reference](https://docs.updog.tech/styling/) for the full varia
 Internal elements use BEM-style class names prefixed with `updog__`. Target them for deep customization:
 
 ```css
-updog-editor .updog__button--primary { background: purple; }
+updog-editor .updog-button--primary { background: purple; }
 ```
 
+There are two prefixes, and they are not interchangeable. Editor-level structure uses `updog__`
+(`updog__data-editor`, `updog__layout`); the controls inside it come from the UI kit and use
+`updog-` (`updog-button`, `updog-button--primary`, `updog-text--md`).
+
 ### Global CSS interaction
 
 Because there is no Shadow DOM, your page's global CSS applies inside the editor. If you have aggressive resets (e.g., `button { all: unset }`), scope them away from `updog-editor` descendants:
@@ -497,7 +515,7 @@ body *:not(updog-editor *) { /* your global rules */ }
 
 ## Notes
 
-- Fonts are inherited from your page. The editor uses `var(--updog-font-family)` which defaults to system fonts.
+- Fonts are inherited from your page. If your app sets no `font-family`, the editor renders in the browser default, which is usually a serif. Set one on your app or on `updog-editor`. (`--updog-font-family` exists and defaults to system fonts, but only the grid's cell-editor input reads it.)
 - In modal mode, the editor portals to `document.body` as a full-screen overlay. In inline mode, it renders in place with no overlay.
 - Multiple `<updog-editor>` instances on the same page are fully independent.