I explored the topic a bit more. Here are the findings. For charts that use iframes (such as LineChart and most of the 'corechart' package, which renders its SVG contents into an iframe created inside the chart container element you specify) there are some limitations in the code that prevent the rendering to occur correctly when the chart code is loaded in a different Window than the one where the chart is placed (as it happens here, where the code is loaded in the background page and the chart is rendered in the popup page, and as it may happen in other multi-frame scenarios).
Also, for charts that rely on additional resources (such as the Table visualization, which loads a style CSS file on the fly when used) such resources as well appear to be added to the Window where the code executes (the background page) rather than the Window where the chart is placed (the popup), resulting in either a non-working or un-styled visualization (depending on the loaded resources). So I'd say that for the moment, the trick of loading the chart API in the background page to speed up the rendering of the extension popup is a no-go. -- R. -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/am6ZkYD0eVkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
