Dominik Moritz

And you can give it a try at https://uwdata.github.io/falcon/flights/. The difference is that resize has a cursor as well (which we don't support yet) and I use `move` instead of...

Vega-Lite does not yet have support for signals. You can modify the Vega, yes.

We now have move cursors over brushes for interval selections thanks to @alliefeldman in #9164.

Odd. To debug this, we should print the dataflow before optimizations and see whether necessary nodes get removed from it.

Yes, I plan to get to these issues this quarter.

I got swamped with other things to work on. I don't have an update yet.

Should be ```json { "$schema": "https://vega.github.io/schema/vega-lite/v5.json", "data": { "url": "data/cars.json" }, "mark": "errorband", "encoding": { "y": {"field": "Miles_per_Gallon", "type": "quantitative"}, "x": {"timeUnit": "year", "field": "Year"}, "tooltip": {"field": "Miles_per_Gallon", "aggregate": "mean"}...

The spec in https://github.com/vega/vega-lite/issues/6184#issuecomment-703856572 works now and we should push it. However, the tooltip doesn't work correctly because we remove the `mean_Miles_per_Gallon` from the compiled Vega spec. It's probably being...

I think the issue may just be in the normalizer. It probably doesn't include the layered field in the name. Can you send a pull request to fix it?

This is the normalized spec. ```json { "$schema": "https://vega.github.io/schema/vega-lite/v4.13.1.json", "data": {"values": [{}]}, "layer": [ { "layer": [ {"name": "LAYERNAME", "mark": {"type": "point"}, "encoding": {}} ], "name": "child__layer_A" }, { "layer":...