The functionality of the "get" method that the metadata plugin overloads is
split out into a "set" method in 1.0.4. Just change the matadata plugin to
overload "set" instead of "get", so it looks like this:
jQuery.fn._set = jQuery.fn.set;
jQuery.fn.set = function(arr){
var result = this._set.apply( this, arguments );
...
Should this be filed as a bug report, or is the matadata plugin not
"official"?
--Erik
On 12/13/06, Erik Beeson <[EMAIL PROTECTED]> wrote:
I can confirm that the metadata plugin doesn't work with 1.0.4. It works
fine with 1.0.3 though.
--Erik
On 12/13/06, Chris Domigan < [EMAIL PROTECTED]> wrote:
>
> I've tried lots of ways:
>
> given: <td class="blah" data="{foo:'bar'}"></td>
>
> $("td.blah").get(0).foo;
>
> $("td.blah").each(function() {
> this.foo;
> });
>
> $("td.blah").each(function() {
> $(this)[0].foo;
> });
>
>
> The point is though, that EVERY jquery "query" on my page, regardless of
> whether or not I'm accessing a metadata attribute, is passing "undefined" to
> the jQuery.fn.get function defined in the metadata plugin, so it's not
> even getting so far as CHECKING whether there is metadata or not. Therefore
> the way in which I'm accessing the metadata seems to be moot at present.
>
> Chris
>
> _______________________________________________
> jQuery mailing list
> discuss@jquery.com
> http://jquery.com/discuss/
>
>
>
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
