On Thu, May 31, 2012 at 8:07 PM, Andrea Dawkins <[email protected]> wrote:
> Thanks for the reply! > > Charts were working fine -- I passed the loader version "1.x". > As far as I understand, "1.x" is a synonym for "1.1", so you were always using the latest release candidate, and not the latest stable version. This week, the charts disappeared again. I assume because of some change > on Google's part, since our code didn't change. > Probably, yes. Thankfully, I found this thread and your comment. > You're encouraged to subscribe to either group or the google-chart-tools-announcements group, where new releases (and release candidates) are announced. I tried setting forceIFrame = false directly, and now it works! > It's weird that setting forceIFrame = false solved your problem, since in 1.1 that's the default value of forceIFrame. I'm confused... If forceIFrame is set to true, it won't work at all on FireFox for either > 1.0 or 1.1. > I tried forceIFrame = true on firefox with both version 1.0 and 1.1, and it worked. Can you provide more details as to which chart you're using, and with what options? Best if you could make a simple HTML the reproduces the problem (preferably in Javascript, not GWT). I am using the GWT wrapper for the google visualizations api. > > I am very impressed with google visualizations, but I want to express my > concern over the fact the code can change out from under a stable release > of the software that uses it. I understand the terms for requiring the > library to be downloaded each time. However, if I can't rely on a > consistent version, it is a PR risk. Can I ask why version numbers aren't > used to version the library? It is strange to even call it a version > number if it just gets replaced with newer versions. If there was a new > number each release, developers could sync their own releases with a > specific api release to ensure consistent behavior and no regressions. > This is a long standing issue. Providing fixed version has many drawbacks, and we still couldn't make it work well. > > > > On Thursday, May 31, 2012 12:55:09 PM UTC-4, Yuval Ronen wrote: >> >> I don't understand. Are your charts broken in 1.0 or 1.1 or both? Does >> changing the value of forceIFrame fixes it? Please let us know if we have a >> bug in 1.1, so we could fix it before the release candidate is released to >> stable. >> >> On Thu, May 31, 2012 at 5:56 PM, asgallant <[email protected]>wrote: >> >>> forceIFrame is a chart option. Previously, most charts were drawn >>> inside iFrames, the new standard is to not use iFrames. Set this option to >>> true to force the charts to draw inside an iFrame. >>> >>> >>> On Thursday, May 31, 2012 10:45:15 AM UTC-4, Andrea Dawkins wrote: >>>> >>>> Yuval, >>>> I had the set the api load option to "1.x" because my GWT wrapped >>>> google visualizations stopped showing up in FireFox. This update must have >>>> broken it again. I am trying to get to the bottom of it, the root cause. >>>> Where can I find the forceIframe boolean, and how does that effect the >>>> output? Is there a canvas option instead? >>>> >>>> Thanks, >>>> Andrea >>>> >>>> >>>> On Thursday, May 24, 2012 11:06:40 AM UTC-4, Yuval Ronen wrote: >>>>> >>>>> Note that this version will flip the default value of the forceIFrame >>>>> option (corecharts, GeoChart, TreeMap, Gauge) from true to false. If you >>>>> relied on the existence of the iframe, we especially recommend testing >>>>> your >>>>> code with the release candidate, and also take into account the existence >>>>> of the iframe is considered an implementation detail, and we might remove >>>>> this option completely in the future. >>>>> >>>>> On Thu, May 24, 2012 at 11:38 AM, Jinji <[email protected]> wrote: >>>>> >>>>>> Release candidate 31.1 of the Google Visualization API was pushed to >>>>>> 1.1 yesterday. >>>>>> >>>>>> Planned release date: 4-Jun >>>>>> >>>>>> Enjoy >>>>>> >>>>>> >>>>> -- >>> 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/-**/RQuXZ6ETD7MJ<https://groups.google.com/d/msg/google-visualization-api/-/RQuXZ6ETD7MJ> >>> . >>> >>> To post to this group, send email to google-visualization-api@** >>> googlegroups.com <[email protected]>. >>> To unsubscribe from this group, send email to google-visualization-api+* >>> *[email protected]<google-visualization-api%[email protected]> >>> . >>> For more options, visit this group at http://groups.google.com/** >>> group/google-visualization-**api?hl=en<http://groups.google.com/group/google-visualization-api?hl=en> >>> . >>> >> >> > On Thursday, May 31, 2012 12:55:09 PM UTC-4, Yuval Ronen wrote: >> >> I don't understand. Are your charts broken in 1.0 or 1.1 or both? Does >> changing the value of forceIFrame fixes it? Please let us know if we have a >> bug in 1.1, so we could fix it before the release candidate is released to >> stable. >> >> On Thu, May 31, 2012 at 5:56 PM, asgallant <[email protected]>wrote: >> >>> forceIFrame is a chart option. Previously, most charts were drawn >>> inside iFrames, the new standard is to not use iFrames. Set this option to >>> true to force the charts to draw inside an iFrame. >>> >>> >>> On Thursday, May 31, 2012 10:45:15 AM UTC-4, Andrea Dawkins wrote: >>>> >>>> Yuval, >>>> I had the set the api load option to "1.x" because my GWT wrapped >>>> google visualizations stopped showing up in FireFox. This update must have >>>> broken it again. I am trying to get to the bottom of it, the root cause. >>>> Where can I find the forceIframe boolean, and how does that effect the >>>> output? Is there a canvas option instead? >>>> >>>> Thanks, >>>> Andrea >>>> >>>> >>>> On Thursday, May 24, 2012 11:06:40 AM UTC-4, Yuval Ronen wrote: >>>>> >>>>> Note that this version will flip the default value of the forceIFrame >>>>> option (corecharts, GeoChart, TreeMap, Gauge) from true to false. If you >>>>> relied on the existence of the iframe, we especially recommend testing >>>>> your >>>>> code with the release candidate, and also take into account the existence >>>>> of the iframe is considered an implementation detail, and we might remove >>>>> this option completely in the future. >>>>> >>>>> On Thu, May 24, 2012 at 11:38 AM, Jinji <[email protected]> wrote: >>>>> >>>>>> Release candidate 31.1 of the Google Visualization API was pushed to >>>>>> 1.1 yesterday. >>>>>> >>>>>> Planned release date: 4-Jun >>>>>> >>>>>> Enjoy >>>>>> >>>>>> >>>>> -- >>> 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/-**/RQuXZ6ETD7MJ<https://groups.google.com/d/msg/google-visualization-api/-/RQuXZ6ETD7MJ> >>> . >>> >>> To post to this group, send email to google-visualization-api@** >>> googlegroups.com <[email protected]>. >>> To unsubscribe from this group, send email to google-visualization-api+* >>> *[email protected]<google-visualization-api%[email protected]> >>> . >>> For more options, visit this group at http://groups.google.com/** >>> group/google-visualization-**api?hl=en<http://groups.google.com/group/google-visualization-api?hl=en> >>> . >>> >> >> -- > 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/-/dooAMguXQlcJ. > 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. > -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. 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.
