Multi view plots do not resize correctly

[sroy3]

Vegalite has limitations on responsive resizing (using the size of the plot's container). These limitations are on multi view plots. There are multiple workarounds to fix this. Some might fix everything, but might be to expensive performance-wise. Others might be more performant, but not make the plots inside resize like other plots completely.

• Change the size in the template. This will have to be done on each window resize as well as plot resize after the size is calculated. The size will need to be calculated in the webview, but the template is in the extension. A delay might appear between the resize of the window or plots and the resize of the actual plot. Changing the template on the webview side might be even worse as it might block the thread.
• We can edit the size of the SVG after its creation. We can go and resize everything needed, but that might be really complicated not knowing how VegaLite calculates everything. We can at least make sure the width and height of the SVG are not smaller than the dimensions of its container.
• We can look into the internals of VegaLite and either fork, patch, or open a pull request to fix the problem.

[sroy3]

I'll create quick prototypes to test for the best solution.

[sroy3]

There is already an issue opened for this on the Vegalite repo. There is even a PR that is requiring some help getting merged. We can maybe take a look at it and help if we can.

[mattseddon]

Decision needs to be made on whether or not we will move to Plotly and when.

[mattseddon]

Change the size in the template. This will have to be done on each window resize as well as plot resize after the size is calculated. The size will need to be calculated in the webview, but the template is in the extension. A delay might appear between the resize of the window or plots and the resize of the actual plot. Changing the template on the webview side might be even worse as it might block the thread.

@sroy3 do you remember if this calculation would be difficult? If we reliably knew where to insert the correct width for a single revision into the plot would this be doable? For some context, we are going to be filling the template on the webview side now. We're also adding anchors for a few different things. If we had an anchor to update the width of an individual plot would that make this achievable?

[sroy3]

Change the size in the template. This will have to be done on each window resize as well as plot resize after the size is calculated. The size will need to be calculated in the webview, but the template is in the extension. A delay might appear between the resize of the window or plots and the resize of the actual plot. Changing the template on the webview side might be even worse as it might block the thread.

@sroy3 do you remember if this calculation would be difficult? If we reliably knew where to insert the correct width for a single revision into the plot would this be doable? For some context, we are going to be filling the template on the webview side now. We're also adding anchors for a few different things. If we had an anchor to update the width of an individual plot would that make this achievable?

I think this could work. Off the top of my head, I don't see why this would be hard to do, but it's been a while since I've been in the codebase.