Bug Tracker

#6124 closed bug (worksforme)

Opened February 19, 2010 08:30AM UTC

Closed October 06, 2010 02:02AM UTC

Last modified January 31, 2011 12:00AM UTC

v1.4 :visible selector

Reported by: eriadam Owned by:
Priority: low Milestone: 1.4.2
Component: selector Version: 1.4.1
Keywords: :visible. :hidden Cc:
Blocked by: Blocking:
Description

I was using this in v1.3.2 and worked perfectly.

$("#sh-ty-container > div:visible")

Now with v1.4 it does not work, the error console says:

Warning: Unknown pseudo-class or pseudo-element 'visible'. Dangling combinator.

Source File: http://dev.mydomain.at/adam.eri/HUT-WEB/trunk/shop/checkout

Line: 0

Actually I got the same error with the :hidden selector.

Warning: Unknown pseudo-class or pseudo-element 'hidden'.

Source File: http://api.jquery.com/visible-selector/

Line: 0

Attachments (0)
Change History (4)

Changed April 07, 2010 04:18AM UTC by hexes comment:1

After update from 1.3.2 to 1.4.2 my selectors (like $("div.ktid_2:visible,div.ktid_4:visible", rc) ) doesn't work. Is it bug or...?

Changed October 06, 2010 02:02AM UTC by addyosmani comment:2

priority: → low
resolution: → worksforme
status: new → closed

Here is a test case that I recreated based on your original submission. As you can see the :visible selector you are trying to use works fine with jQuery 1.4.2.

http://jsfiddle.net/5sKbe/

http://jsfiddle.net/5sKbe/2/

Here you can similarly see :hidden working as expected:

http://jsfiddle.net/5sKbe/1/

Closing as this works for me.

Changed January 30, 2011 11:03PM UTC by uli.riehm@metadea.de comment:3

As of jQuery 1.4.4, using Firefox 4b10 the warning is still alive! I've tried both your fiddles.

Changed January 31, 2011 12:00AM UTC by danheberden comment:4

_comment0: \ But no errors - if FF chooses to display a warning if JQ tries to use a possibly present pseudo selector that's the prerogative of the browser. If it was an error, then yeah, that'd be a problem. Load up firefox.com in 4b10 - and watch the warning fly... \ → 1296432088067487

But no errors - if FF chooses to display a warning if JQ tries to use a possibly present pseudo selector that's the prerogative of the browser. If it was an error, then yeah, that'd be a problem. Load up firefox.com in 4b10 - and watch the warnings fly...