exposedProps again with only Effects Scale
[right so time, non-disclosure and excessive deep complexities keep me from simply demonstrating this with jsFiddle again, but I'll try to bring awareness since I've gotten a little closer to this problem I think.]
with only a complex call to a scale effect completely isolated in a jq UI's custom, the line 322 in jQuery 1.8.2
src = target[ name ];
will result in an _exposedProps_ error in Firefox 15.0.1
stack inspection shows when I call to show scale with this...
targ[fn](fx, ao, (tSpeed * 1000));
where targ is the div, fn is 'show' fx = 'scale' ao is an attribute object (extracted from dynamically loaded XML via parsing with JSON) with percent 100 and an array with origin set to bottom and center!?
Upon the exposedProps violation the 'name' is set to 'ec.storage.position', while the target is an empty object, which of course results in src being undefined.
I think you might be able to hack jq 1.8.2 to stop at a break point if and when said conditions are met.
Anyway I'm not really capable of understanding way an empty object being asked for a none existing attribute/property that results in src getting undefined is considered a exposed Property violation which seems to be that really there's something wrong with the error itself (and so therefore maybe this needs to be communicated to Firefox) but it does (often in various similar situations). It's difficult to track down, and for now everything works (because it's just a warning) but the warning suggest it could and will eventually blow up in mine and others faces if used.
At this point not not only was I unable to use jQuery Mobile (same errors) but also anything jQuery UI looks out of bounds to me. Ironically if I custom build what and when I need it I suspect it won't notice a problem or will be able to fix it being an internal issue. I would rank this pretty high up, since at least for me it means I won't be using it.
Testing against jqui (custom scale only) 1.8.24 as of today with jq 1.8.2 (all current versions).