[
https://issues.apache.org/jira/browse/SHINDIG-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562313#action_12562313
]
Bruno Bowden commented on SHINDIG-37:
-------------------------------------
Anything we can do to minimize the work needed by a developer to support Caja
is a very good thing. Furthermore as Caja improves, we'll be able to Cajole
more and more gadgets without developer modifications. If that Gadget can
become Cajoled without the author having to work on it, that would be great.
What concerns me is that many of the Caja failures are likely to be at run time
instead of compile time. So should a gadget author have the ability to ask for
their gadget not to be Cajoled incase they know it doesn't work? If don't give
that option, we may need to monitor Caja runtime failures and fall back to the
iFrame for certain gadgets.
> Caja feature javascript is not included when forcing cajoling through &caja=1
> -----------------------------------------------------------------------------
>
> Key: SHINDIG-37
> URL: https://issues.apache.org/jira/browse/SHINDIG-37
> Project: Shindig
> Issue Type: Bug
> Components: Gadgets Server - Java
> Reporter: Christopher Rohrs
> Assignee: John Hjelmstad
> Priority: Minor
>
> Caja does not work for simple non-OpenSocial gadgets like
> http://www.google.com/ig/modules/hello.xml. In particular, I get a JS error
> because "___" is not defined. It appears that caja.js is only included if
> <Require feature="opensocial-samplecontainer">. This should not be the case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
