The bug tracker is back up again - feel free to add this as a bug!
--John
On 5/9/07, John Resig [EMAIL PROTECTED] wrote:
I agree then, it is inconsistent. Once I get the bug tracker up, this
should go in.
--John
On 5/9/07, Arrix [EMAIL PROTECTED] wrote:
The .removeClass() behavior is good.
Glad to see the trac up and running:-) Ticket created
herehttp://dev.jquery.com/ticket/1167.
On 5/11/07, John Resig [EMAIL PROTECTED] wrote:
The bug tracker is back up again - feel free to add this as a bug!
--John
On 5/9/07, John Resig [EMAIL PROTECTED] wrote:
I agree then, it is
No, that's expected. removeClass() was re-worked such that
.removeClass(one) would remove one class, .removeClass(one two)
would remove two classes, and .removeClass() would remove all classes.
This is very similar to how .unbind() works (if you call it with no
arguments, it removes all bound
The .removeClass() behavior is good. But I don't think .removeClass()
should remove every class.
Though it doesn't make sense to write .removeClass(), sometimes the
parameter passed to .removeClass is a variable
$('#someId').removeClass(classToRemove);
classToRemove may be set to by previous
I agree then, it is inconsistent. Once I get the bug tracker up, this
should go in.
--John
On 5/9/07, Arrix [EMAIL PROTECTED] wrote:
The .removeClass() behavior is good. But I don't think .removeClass()
should remove every class.
Though it doesn't make sense to write .removeClass(), sometimes
5 matches
Mail list logo