Chatted with Jasvir. He says it does not include a fix for that issue. This patch should be fine however.
On Tue, Jun 23, 2009 at 12:57 PM, Paul Lindner <lind...@inuus.com> wrote: > I'm not sure if it does. Is there another issue open for that? > > On Mon, Jun 22, 2009 at 6:35 PM, Louis Ryan <lr...@google.com> wrote: > > > Does the updated Caja binary have a fix for the CSS DOM cloning issue? > > > > On Mon, Jun 22, 2009 at 5:42 PM, Paul Lindner (JIRA) <j...@apache.org > > >wrote: > > > > > > > > [ > > > > > > https://issues.apache.org/jira/browse/SHINDIG-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722916#action_12722916 > > ] > > > > > > Paul Lindner commented on SHINDIG-822: > > > -------------------------------------- > > > > > > Is there any reason that I shouldn't apply this patch? > > > > > > Been sitting around quite a while.. > > > > > > > > > > Remove caja's dependence on opensocial feature > > > > ---------------------------------------------- > > > > > > > > Key: SHINDIG-822 > > > > URL: > https://issues.apache.org/jira/browse/SHINDIG-822 > > > > Project: Shindig > > > > Issue Type: Improvement > > > > Components: Java, Javascript > > > > Reporter: Jasvir Nagra > > > > Attachments: remove-caja-opensocial-dependence.patch > > > > > > > > > > > > Moves caja container setup out of > > > features/opensocial-reference/container.js to features/caja/caja.js. > As > > a > > > result caja gadgets can run cajoled without requiring opensocial. > > > > Feature libraries can use caja.tameModule___() to register a function > > > which gets called to tame their api. > > > > The pom changes updates the version of caja to one which supports > > cajoled > > > versions of prototype and jquery. > > > > > > -- > > > This message is automatically generated by JIRA. > > > - > > > You can reply to this email to add a comment to the issue online. > > > > > > > > >
