Ok I looked into this a bit more.  The code is working as intended,
$.support.boxShadow is being set to a string in the cluetip initialization.

I found out what was setting this property to true, and it is the jquery
mobile plugin. It seems that jquery mobile is just following the precedent
set by the other existing properties of the support object in setting the
property to true or false.

A couple of suggestions:

It might be best to just go along with this to avoid future conflicts with
other plugins, and set to true or false if it doesn't exist,  then store
the flavor of the supported box-shadow in a separate property somewhere.

Or you could  just keep the code the same a create a new property just for
cluetip that would be less likely to be overwritten by another plugin.





On Sat, Sep 7, 2013 at 2:14 PM, Karl Swedberg <notifications@github.com>wrote:

> In jquery.cluetip.js:
>
> > @@ -829,7 +829,8 @@
> >            dsStyle = '1px 1px ' + dropShadowSteps + 'px rgba(0,0,0,0.5)';
> >          }
> >          var dsOffsets = dropShadowSteps === 0 ? '0 0 ' : '1px 1px ';
> > -        $cluetip.css($.support.boxShadow, dsStyle);
> > +
> > +        $cluetip.css('box-shadow', dsStyle);
>
> I'm having a hard time seeing how $.support.boxShadow would be set to trueunless another script is doing that. The cluetip plugin only ever sets it
> to a string. It's also checking for a vendor-prefixed property if the
> standard one doesn't exist. Maybe that's not so important anymore, but I
> can't just assume that unprefixed "box-shadow" will work if I'm checking
> for the vendor-prefixed ones as well. Can you show me where the plugin is
> exhibiting the problem?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/kswedberg/jquery-cluetip/pull/134/files#r6225306>
> .
>