Bug Tracker

Ticket #7291 (closed bug: wontfix)

Opened 4 years ago

Last modified 3 years ago

Unknown pseudo-class or pseudo-element 'sizzle'.

Reported by: csnodgrass3147@… Owned by:
Priority: undecided Milestone: 1.5
Component: selector Version: 1.4.3
Keywords: Cc:
Blocking: Blocked by:

Description

Using Firefox 3.6.11 and jQuery v1.4.3, the error console gives the following CSS warning:

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

It is given this even on a blank page that just includes the library.

Change History

comment:1 follow-up: ↓ 3 Changed 4 years ago by john

  • Status changed from new to closed
  • Resolution set to wontfix

Yep - unfortunately this is an issue with Firefox - for some reason they throw an uncatchable warning that we can't prevent (they should be throwing an exception that we can catch).

comment:2 Changed 4 years ago by anonymous

Has a bug been reported to Firefox regarding this issue?

comment:3 in reply to: ↑ 1 Changed 4 years ago by anonymous

Replying to john:

Yep - unfortunately this is an issue with Firefox - for some reason they throw an uncatchable warning that we can't prevent (they should be throwing an exception that we can catch).

Firefox 3.6.11 and IE 8 both have this issue with jQuery 1.4.3. I had to rollback to jQuery 1.4.2. This needs more attention.

comment:4 follow-up: ↓ 6 Changed 4 years ago by Diemuzi

I agree, this needs more attention as it does not occur with 1.4.2, but it does with 1.4.3 which means something changed in the jQuery code-base that is causing this. I don't rule out that FF could play a role in this but testing with the newest FF and 1.4.2 this exception does not happen.

comment:5 in reply to: ↑ description Changed 4 years ago by anonymous

Replying to csnodgrass3147@…:

Using Firefox 3.6.11 and jQuery v1.4.3, the error console gives the following CSS warning:

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

It is given this even on a blank page that just includes the library.

comment:6 in reply to: ↑ 4 Changed 4 years ago by anonymous

Replying to Diemuzi:

I agree, this needs more attention as it does not occur with 1.4.2.

Firefox or not Firefox. We had 'charcode' warning and now this. No one wants sites with warnings. jQuery team should reconsider its support for FF. This doesn't look good and may even discourage some people from using this framework.

comment:7 Changed 4 years ago by rwaldron

Can you test this with 1.4.4rc2? Thanks!

comment:8 Changed 4 years ago by csnodgrass3147@…

Using the latest version from GIT (which I'm guessing is 1.4.4rc2) it does seem to be fixed using Firefox version 3.6.12.

comment:9 Changed 4 years ago by rwaldron

  • Component changed from unfiled to selector

That's great news. The ticket can remain closed. :D

comment:10 Changed 4 years ago by anonymous

Opera 10.63 with 1.4.3:

HTML style attribute
Unknown pseudo class
Line 1:
  #__sizzle__ >ul:hidden
  ----------------------^

waiting for 1.4.4

comment:11 Changed 4 years ago by snover

Warnings don’t mean anything. When you use jQuery’s custom pseudo-selectors, you are knowingly passing an invalid CSS selector. If you don’t want to see warnings about it, never ever use any of the custom pseudo-selectors. Otherwise, ignore it—it’s normal, and it doesn’t harm a thing.

comment:12 Changed 4 years ago by csnodgrass3147@…

Warnings do mean something...

And in this case, the warning occurs simply by including jQuery, whether or not you use sizzle.

However, this problem seemed to be fixed with the latest version and so it's a moot point now.

comment:13 Changed 4 years ago by anonymous

Well, true, with 1.4.4 *this* warning was gone, but instead we've got:

Warning: Unexpected token in attribute selector: '!'.

And it's the same with 1.5 :-(

Last seen in FF 3.6.13

I can't help but think these issues are related. And I think to recall that it was about the transition to 1.4 that these mysterious browser warnings started.

comment:14 Changed 4 years ago by anonymous

A site may continue to function with warnings, but if they can be eliminated, they should be. Another side affect of all these warnings seems to be that the page loading icon perpetually runs in the page's tab. If I'm a user, I'm used to seeing a page loaded icon once the page is complete, and having the icon and status bar telling me that it's still loading is unsettling. Am I free to proceed or not? After getting rid of the code causing the warnings, the page loading appears to complete without a hitch.

comment:15 Changed 3 years ago by zlati.pehlivanov@…

well i have

Unknown pseudo class
  [id='__sizzle__'] :input,a
  ------------------------^

with latest version of opera 11.52 and jquery 1.6.3

Can't understand what can cause this error. It keeps bubbling in the error log.

Note: See TracTickets for help on using tickets.