Ariel,
Thanks for pointing this out.
Since only simple selectors are supported, perhaps it would be less
confusing if complex selectors returned undefined or null (consistent
with the recent discussion about .attr()), instead of true?
Jed Schmidt
[EMAIL PROTECTED]
On May 25, 1:51 am, Ariel
/ all return true, even though the body element
// isn't a child or sibling of a div element
jQuery("body").is("html#nonexistentid *")
// returns true, even though the html element has no id
Is the .is() method supposed to support selectors with hierarchical
relationships?
Jed Schmidt
[EMAIL PROTECTED]
; a selector, and then another
function to operate on the matching nodes.
jQuery currently ignores all text nodes during selection, so a custom
selector is out of the question now, but do you think it'd be possible
to add support for a text node selector such as ":text" at some point
in
I love how succinct jQuery can be, but given how long I worked on
this, it's kinda frustrating how it makes everything look so easy...
Jed Schmidt
On Aug 12, 1:23 am, Jed Schmidt <[EMAIL PROTECTED]> wrote:
> Thanks for the tip, John.
>
> Maybe I don't quite grok it,
all text nodes
themselves, regardless of whether they are the sole children of their
parent node. Since jQuery ignores text nodes, I think I would have to
use a custom traverse function instead. Does this make sense?
Jed Schmidt
On Aug 12, 12:50 am, "John Resig" <[EMAIL PROTECTE
bjects for its text
node children, and then removes the original element. Can something
like this be done in jQuery?
Thanks again for any advice,
Jed Schmidt
d put every
character in it's own span node, so any ideas/feedback would be
appreciated.
Jed Schmidt
[1] http://developer.mozilla.org/en/docs/DOM:element.nodeName#Notes
[2] http://www.w3.org/TR/xpath#node-tests
7 matches
Mail list logo
