I see what you're saying. You're worried that because there's a
difference here, there might be a differnce in a non-broken document that
we haven't found yet.
Personally, I wouldn't worry about it until/unless there's an actual use
case that's having this same problem on a non-broken DOM.
- Bri
> Now, my mark-up is wrong. I should have wrapped the nested
> in it's own , but I missed it. Testing looked good
> in FF 2, .next() was returning the nested , and I didn't
> even notice the problem. In IE6/7 however,
> .next() returned the next , and not the which was in
> fact next the n
That's not what I'm looking for at all. The point was whether or not .next()
is always returning the correct element in a given situation. It was merely
a concern, not a request to make jQuery work on broken docs.
Adam
Citrus wrote:
>
> It's hard enough to get everything working properly for
It's hard enough to get everything working properly for documents that are
well-formed. I don't think that it's worth the effort to force
consistency in how jQuery handles broken documents. If you do anything on
top of an invalid DOM, you can't make the results predictable. Even if
you could, th
The mark-up:
The js:
$('li.expandable')
.bind('click', function(){ $(this).next().slideToggle('fast'); })
.next().hide()
;
Now, my mark-up is wrong. I should have wrapped the nested in it's own
, but I missed it. Testing looked good in FF 2, .next() was returning
t
