Bug Tracker

Ticket #12311 (closed bug: fixed)

Opened 2 years ago

Last modified 2 years ago

jQuery 1.8 and .is(":visible")

Reported by: anonymous Owned by: anonymous
Priority: low Milestone: 1.8.1
Component: selector Version: 1.8.0
Keywords: Cc:
Blocking: Blocked by:

Description

After updating for jQuery 1.8 I noticed the .is(":visible") returning false for a visible input on Firefox 3.6.22 and returning true for a visible input on Firefox 14.0.1

Firefox 3.6.22 alert(false) ->  http://jsfiddle.net/qVntx/

Firefox 14.0.1 alerts(true) ->  http://jsfiddle.net/qVntx/

Change History

comment:1 Changed 2 years ago by dmethvin

  • Owner set to anonymous
  • Status changed from new to pending

Firefox 3.6 is no longer supported by Mozilla or jQuery. Sounds like it works okay for recent versions?

comment:2 Changed 2 years ago by timmywil

  • Priority changed from undecided to low
  • Resolution set to fixed
  • Status changed from pending to closed
  • Component changed from unfiled to selector
  • Milestone changed from None to 1.8.1

It is supported by Sizzle and this issue has been fixed in Sizzle upstream.

comment:3 Changed 2 years ago by anonymous

@dmethvin "Firefox 3.6 is no longer supported by Mozilla or jQuery"

I don't see anything here ->  http://blog.jquery.com/2012/08/09/jquery-1-8-released/ Or here ->  http://imageshack.us/photo/my-images/198/supportym.jpg/

And yes, it looks ok for the recent versions...

comment:4 Changed 2 years ago by dmethvin

 https://blog.mozilla.org/futurereleases/2012/03/23/upcoming-firefox-support-changes/

If Mozilla doesn't support the browser, jQuery doesn't either. It *may* work, but we are no longer unit testing against Firefox 3.6 so there are likely to be regressions.

comment:5 Changed 2 years ago by rwaldron

@anonymous, removing Firefox 3.6 support is a very recent change. Apologies that the main page isn't up-to-date

comment:6 Changed 2 years ago by anonymous

Actually I did knew the support would be droped soon, but I thought it would be mentioned in the changelog. It is a good idea to perhaps avoid future tickets.

comment:7 Changed 2 years ago by dmethvin

Good point, we should have mentioned it and are in the process now of updating the home page.

Note: See TracTickets for help on using tickets.