why are you using the document.domain attribute? is this page displayed as
an iframe in another webpage?


On Thu, Oct 27, 2011 at 12:40 PM, David Iglesias <[email protected]> wrote:

> I have created a ticket for this issue:
>
>
> http://code.google.com/p/google-visualization-api-issues/issues/detail?id=726
>
> Regards!
>
>
>
> On Wed, Oct 26, 2011 at 6:29 PM, David Iglesias <[email protected]> wrote:
>
>> Hey guys!
>>
>> We managed to isolate the problem and prepared a quick test case for you
>> to look at :)
>>
>> The problem is that we need to set the document.domain property (to do
>> cross-domain stuff) and that is confusing IE, because the iframe that is
>> used for rendering does not set the same document.domain that we have in our
>> page.
>>
>> Example:
>> http://www.ditman.net/charts/ (works with FF, Chrome, fails with IE)
>>
>> If you feel especially crafty (or a Google engineer sees this) we traced
>> the issue to the line 862 of the minimized file, where it does:
>>
>> this.Nc=new vs(this.Db,b)
>>
>> Inside that new vs, a method named "this.At" gets called, (defined as V.At
>> in line 613). That method sets the properties of the iframe and appends it
>> inside the container div with this code:
>>
>> this.Db[r](c)
>>
>> Right after that, it tries to access the contents of the iframe with this:
>>
>> var d=c.contentDocument;
>> d||(d=c.contentWindow[gc]);
>>
>> The second line ends up throwing an "Access denied" exception that finally
>> gets rendered as "Your browser does not support charts".
>>
>> The solution?
>>
>> We should be able to pass a document.domain for the iframe so it applies
>> it inside the "V.At" method before it gets injected into the DOM (maybe as a
>> parameter when creating the graph object, or as an additional parameter to
>> the draw() method?)
>>
>> What do you think? Any workarounds to this issue? :)
>>
>> Regards!
>>
>>
>>
>> On Wed, Oct 26, 2011 at 3:40 PM, David Iglesias <[email protected]> wrote:
>>
>>> Hey all!
>>>
>>> The gallery is visible in the problematic browser (ie9) just fine (of
>>> course :P)
>>>
>>> The problem in our side happens when drawing the chart... API
>>> initialization, graph creation and datatable creation work just fine.
>>>
>>> I'm currently building a static version of the problematic part of the
>>> site and disable scripts one by one to see which one is the offender (we
>>> must be doing something weird on our JS, but I'm not sure what, that was why
>>> I was wondering if anybody knew the reasons the API would throw the error in
>>> the first place :P)
>>>
>>> Regards!
>>>
>>>
>>>
>>> On Tue, Oct 25, 2011 at 10:40 PM, NA <[email protected]> wrote:
>>>
>>>> You can always check the browser compatability by visiting the Chart
>>>> Gallery and seeing if you can view the charts:
>>>>
>>>>  http://code.google.com/apis/chart/interactive/docs/gallery.html
>>>>
>>>> That's a good way to make sure the API is still working, and a way of
>>>> confirming that a browser is capable of displaying the charts.
>>>>
>>>> --
>>>> 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.
>>>>
>>>>
>>>
>>
>  --
> 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.
>

-- 
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.

Reply via email to