Jimbo

Agreed on the utility of a `.clear()` method. This seems to be a common enough case to make an API for it. In the meantime, one workaround is to `.bind()`...

Proposed API: ```ts selection.onClick((e: MouseEvent, s: SpriteView, d: Datum, index: number, arry: Datum[]) => { /* ... */ }); selection.onMouseover((e: MouseEvent, s: SpriteView, d: Datum, index: number, arry: Datum[]) =>...

> However, elements in a MegaPlot Selection all get mapped to the same canvas element, which doesn't inherently afford per-datum mouse event associations, Yes, the underlying DOM events would be...

Just ran into this myself. Is there a way to silence the warning?

Workaround: You can disable Lit plugin's CSS validation checks entirely by adding the following configuration to your `tsconfig.json`: ```json { "compilerOptions": { "plugins": [ { "name": "ts-lit-plugin", "rules": { "no-invalid-css":...

The root cause is the version of `vscode-css-languageservice`. The current latest version of lit-analyzer (2.0.3) depends on vscode-css-languageservice v4.3.0. However the latest version of vscode-css-languageservice at the time of this...

In another effort to work around this problem, I uninstalled the VSCode lit plugin and tried the `ts-lit-plugin` option instead. However I can't get it to work. Visual Studio reports...

Update: This problem is only with the deployed versions and has been fixed in head. So if you build and package from source, you can install from the built `packaged.vsix`...

One more note. This is my first time using `@container` queries and it took some fiddling to figure out how to work it with the shadow DOM. Here's a minimum...