Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
I would like to request this is deleted as I have now solved the issue on the
forums.
Original comment by brain2006@gmail.com
on 28 Aug 2008 at 1:55
Let's turn it into a documentation improvement request. For details, read
http://groups.google.com/group/simile-widgets/browse_thread/thread/3ac433098241d
1d8
Original comment by nicolas....@logilab.fr
on 29 Aug 2008 at 8:37
documentation enhancement
Original comment by nicolas....@logilab.fr
on 14 Sep 2008 at 7:05
Hi,
this is not solved, there is a problem with https and IE
check this
http://groups.google.com/group/simile-widgets/browse_thread/thread/881cda3608554
20f
Thanks
Original comment by tang...@gmail.com
on 22 Sep 2008 at 10:48
Need a test case--please supply an html file which causes the error message
about
secure/insecure when loaded via https transport, but works properly otherwise.
You can store the test case file as a page for the Google Group, see
http://groups.google.com/group/simile-widgets/web
Thanks,
Larry
Original comment by larryklu...@gmail.com
on 22 Sep 2008 at 5:00
Original comment by larryklu...@gmail.com
on 22 Sep 2008 at 5:02
Hi,
it´s pretty easy to replicate the problem with cubism example.
Just create a var named json inside cubism.html and copy all the content from
cubism.js to that var. Invoke the load with
eventSource.loadJSON(json,'');
call this in IE using https and you will see the anoying warning.
I have made this and created an cubism2.html file. just copy this file to cubism
folder and you are ready to go.
Thanks :)
Original comment by tang...@gmail.com
on 23 Sep 2008 at 9:12
Attachments:
I´ve added also the file to the link you provided.thanks
Original comment by tang...@gmail.com
on 23 Sep 2008 at 9:14
another issue I´ve noted related to var loading instead of json file, is that
the
'loading' indicator does not shows while processing the data.
Thanks
Original comment by tang...@gmail.com
on 26 Sep 2008 at 8:12
Original comment by stefano.mazzocchi@gmail.com
on 25 Mar 2009 at 7:01
I´ve checked and this still happens in IE8
Original comment by jorgecor...@gmail.com
on 25 Mar 2009 at 9:28
Hi,
This error is gone in timeline 2.3.1.
Anyway I think it´s better to invoke
eventSource.loadJSON(json,document.location.href);
instead of
eventSource.loadJSON(json,'');
As I´ve saw in on of the examples.
Original comment by jorgecor...@gmail.com
on 30 Mar 2009 at 1:45
Closing per suggestion of jorgecorreia1.
I created a wiki page that discusses this topic.
I think the problem was being caused by people using
eventSource.loadJSON(json,'');
instead of
eventSource.loadJSON(json, document.location.href);
Original comment by larryklu...@gmail.com
on 30 Mar 2009 at 7:50
Original issue reported on code.google.com by
brain2006@gmail.com
on 28 Aug 2008 at 10:23