Kanit Wongsuphasawat
Kanit Wongsuphasawat
Seeing #7654, I still feel like the option c) is probably the right long term solution. After all, I think the teaching argument that we need to align with steven's...
TODO: let's also handle categorical -- we should keep the old behavior for categorical
For now I'll drop `"tooltip": {"content": "encoding" }` in the output (https://github.com/vega/vega-lite/pull/6442) To ignore the tooltip directive for marks with no associated data, we need to add such support in...
Given that it's so similar to `display` in CSS -- I wonder if the right encoding channel name should be `display` (rather than `enabled` / `disabled`)?
I know that it's not exactly the same as we won't have `display: block`, etc. but I still like it as a name better than `enabled` / `disabled`
I kinda find the term `defined` a bit misleading for enabling/disabled other marks though. For line/trail/area, skipping a point because it is not "defined" sound reasonable. But say if you...
> Display could be confusing because I would think it applies to the whole feature, which becomes weird if you base it on datum rather than just signals. I don't...
From a discussion in https://github.com/vega/vega/issues/1367, it seems like `"none"` is not a good option as it is not supported in HTML5 Canvas (at least on Chrome).
Ok I thought something is wrong with my computer. lol
File a bug in Vega?