David Anthoff

Hm, maybe the HTML that we generate isn't properly resizing the containing container? [This](https://github.com/queryverse/VegaLite.jl/blob/master/src/rendering/render.jl#L20) is the HTML that gets used when things are shown in the browser. @domoritz, are there...

@domoritz [Here](https://gist.github.com/davidanthoff/7221d231c5fc44abb859b3abc0a5717f) is an HTML file with this. @oheil I don't think it is a versioning thing, `VegaLite#master` should bring the latest versions of the packages along. But I do...

I think we should just change that in VS Code and ElectronDisplay as well, those are not complicated changes at all :) Those are the three "clients" we have on...

Ok, I fixed this in VS Code, see https://github.com/julia-vscode/julia-vscode/pull/932. @TonyLianLong could you make a similar adjustment for ElectronDisplay, if we need it? @oheil are you preparing a PR for the...

@oheil, ah, that is kind of annoying, but maybe not the end of the world? @domoritz, any idea how we might get around this vega embed placement issue?

Uh, that is not great...

Couldn't this be solved that the container of the parent element that will host the `div` that gets the vega stuff is always auto resizing, and then the vega/vega-lite code...

Check out https://github.com/tkf/VegaStreams.jl, I think it essentially does all that :)

I think the easiest way to do this is to use the [facet operator](), not the column encoding channel. That would look like this: ````julia df |> @vlplot(facet={column={field=:col, typ=:nominal}}) +...

I think support for different data sources should be working with the julia package, I believe that worked with vegalite.js pre 3.0 already. The way to do this is to...