It was intentional in that in the places where we use it we weren't concerned with properties bleeding through from prototypes. I will make a note of it in the documentation and we can re-examine this after 1.4 is out.
http://api.jquery.com/jQuery.isEmptyObject/ --John On Tue, Jan 12, 2010 at 4:50 PM, Sidney San Martín <s...@sidneysm.com> wrote: > I notice that jQuery.isEmptyObject() in 1.4rc1 uses an unfiltered > for...in, so it'll pick up on inherited properties. Is this > intentional? Is so, maybe it should be documented or there should be a > flag on isEmptyObject() to only look at the object's own properties. > > -- > You received this message because you are subscribed to the Google Groups > "jQuery Development" group. > To post to this group, send email to jquery-...@googlegroups.com. > To unsubscribe from this group, send email to > jquery-dev+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/jquery-dev?hl=en. > > > >
-- You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-...@googlegroups.com. To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
