Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 482235
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T01:04:33+00:00 2026-05-13T01:04:33+00:00

I recently have discovered a warning happening in Firefox that says Warning: Unknown pseudo-class

  • 0

I recently have discovered a warning happening in Firefox that says

Warning: Unknown pseudo-class or pseudo-element ‘hidden’

Here is page http://eleven23.net/eleven23/beta/work/web/lounge22.php

And the warning happens when it gets to the part of javascript that has img:hidden

$(‘img:hidden’).eq(0).fadeIn(500);//fades in the hidden images one by one
i++;//add 1 to the count

So Im wondering if anyone has an idea on how to resolve this warning.

Thanks!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-13T01:04:33+00:00Added an answer on May 13, 2026 at 1:04 am

    The first step is to really stop the repeated calling of doThis() via setInterval which at the moment doesn’t happen. Thus the warning appears every 500ms.

    Change

    $(document).ready (function() {
      var int = setInterval("doThis(i)",500);
    });
    

    to

    $(document).ready (function() {
      int = setInterval("doThis(i)",500);
    });
    

    Else your call to clearInterval(int) won’t do anything as you declared var int twice and try to clear the “outer” int which isn’t the interval.

    After this fix only 4-5 of this warning should remain in your console.


    Now to your error. There isn’t much you can do to stop this error from appearing exactly that many times you call doThis().

    jQuery uses Sizzle internally as selector engine. And in some cases Sizzle tries to use (on browsers supported) the querySelectorAll() function to find the elements matching your selector.

    Now AFAIK is hidden not a valid CSS selector thus although Firefox supports the call to querySelectorAll() it correctly fails after encountering an unknown selector. jQuery catches the error and then does the selection of image:hidden itself.

    If you don’t want to see this error at all you can use a different jQuery syntax which in this case would stop Sizzle from trying to attempt to use querySelectorAll().

    Change

    $('img:hidden').eq(0).fadeIn(500);
    

    to

    $('img:hidden', $('div#content_wrapper')).eq(0).fadeIn(500);
    

    But I don’t advise you to do this as it doesn’t really get you much only 4-5 warnings less in your console.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I recently discovered that when you have a page set to session readonly and
I have recently discovered that when I have pointers within a class, I need
I have recently discovered that I am affected by this bug http://www.mail-archive.com/mono-bugs@lists.ximian.com/msg71515.html Well, at
I recently discovered that all Windows 7 machines have an handwriting recognition API within
I've recently discovered that MVC is supposed to have two different flavors, model one
I have discovered recently that's possible to call anoymous blocks from jdbc like this:
We have recently discovered that when we run a lot of different processes on
I have recently discovered that I was using my third party diff/merge tool incorrectly
Recently I have discovered that my release executable (made with msvc++ express 2008) becomes
I've just recently updated my PHP to a newer version and have discovered that

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.