Bug Tracker

Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#7555 closed bug (duplicate)

Incorrect .is() behavior when checking for attribute with no value

Reported by: [email protected] Owned by:
Priority: low Milestone: 1.next
Component: selector Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:

Description

Given this markup:

<div data-hi></div> <div data-hi></div>

Running this code:

$('div').is('[data-hi]');

should return true, since .is() returns true if any member of the collection matches its query. But it returns false.

This is illustrated here: http://jsfiddle.net/ujP2Y/8/

See also #5930.

Change History (6)

comment:1 Changed 11 years ago by Alex Kahn <[email protected]…>

Note that this bug only happens if the there are multiple elements in the collection matching the attribute query. If just one element has the attribute, .is() works as expected.

comment:2 Changed 11 years ago by Rick Waldron

Component: unfiledselector
Milestone: 1.51.4.5
Priority: undecidedlow
Status: newopen

comment:3 Changed 11 years ago by ajpiano

This fiddle illustrates just how anomalous this is, for anyone who is curious. http://jsfiddle.net/ajpiano/qUwL7/

comment:4 Changed 11 years ago by jitter

Same test as by ajpiano but more browsers tested http://www.jsfiddle.net/jitter/CnJPA/

comment:5 Changed 10 years ago by john

Resolution: duplicate
Status: openclosed

comment:6 Changed 10 years ago by john

Duplicate of #5637.

Note: See TracTickets for help on using tickets.