On Thursday, May 31, 2012 1:45:38 PM UTC-4, Yuval Ronen wrote: 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. > The only explanation I can surmise is that the loader gave me a variation other than 1.1. I found the 1.x piece of advice somewhere buried in these messages awhile back. Other than that, I'm not sure.
> You're encouraged to subscribe to either group or > the google-chart-tools-announcements group, where new releases (and release > candidates) are announced. > Good idea! I will definitely subscribe. However, the latest knowledge won't help our already released software versions in the field. It's weird that setting forceIFrame = false solved your problem, since in > 1.1 that's the default value of forceIFrame. I'm confused... > I agree, weird... Whatever the explanation, it is working now with that boolean set explicitly on the options. This is a long standing issue. Providing fixed version has many drawbacks, and we still couldn't make it work well. I understand. I hope this is still on your roadmap, because it has definite implications in the field. I realize this error was something special about my implementation, but it worked before... it would be nice to have a controlled release so something doesn't suddenly break on us. :) Thanks again for your quick responses. > > >> >> >> >> 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 view this discussion on the web visit https://groups.google.com/d/msg/google-visualization-api/-/DUboUEUjGDIJ. 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.
