Side navigation
#7888 closed bug (worksforme)
Opened January 03, 2011 01:01PM UTC
Closed January 06, 2011 05:57PM UTC
Last modified January 09, 2011 07:44PM UTC
.is(':visible') returns different values for different browsers
| Reported by: | anonymous | Owned by: | anonymous |
|---|---|---|---|
| Priority: | undecided | Milestone: | 1.6 |
| Component: | unfiled | Version: | 1.4.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Hi,
I noticed that the method .is(':visible') returns a different value for some specific versions of browers. The error was reported by a user using my application, he's using FF 3.6.10, but I tested on it and don't get the problem ... so maybe there are different versions of 3.6.10 (depending to the country?)
Attachments (0)
Change History (6)
Changed January 03, 2011 02:10PM UTC by comment:1
| owner: | → anonymous |
|---|---|
| status: | new → pending |
Changed January 03, 2011 02:24PM UTC by comment:2
| status: | pending → new |
|---|
Unfortunately, the user is not located at the same place as mine, I can't reproduce the issue. I can for now only give one additional detail: the user upgraded to Firefox 3.6.10 and still has this issue (.is(':visible') returning true for him). He then downloaded Chrome and on Chrome it returns false (normal behaviour). But anyway he is restricted to use Mozilla, so I must find a solution to his problem. I may come back with additional details (platform, etc.)
Changed January 03, 2011 02:39PM UTC by comment:3
Sorry I meant from 3.6.10 he upgraded to 3.6.13 (which is latest at the moment I write).
Changed January 06, 2011 05:57PM UTC by comment:4
| resolution: | → worksforme |
|---|---|
| status: | new → closed |
Tested with jQuery 0 GIT
Changed January 09, 2011 06:39PM UTC by comment:5
Of course it works for you and for me too. But for that specific client I can assure you it doesn't. Anyway, I can't provide code to reproduce the error.
Instead of testing the visibility of the element with ":visible", I use a class "visible" and "hidden" and use hasClass instead.
Changed January 09, 2011 07:44PM UTC by comment:6
We cannot do anything to solve a bug that happens only via hearsay and can't be reproduced. It would be awesome if we could, but we're just developers, not psychics :)
Thanks for submitting a ticket to the jQuery Bug Tracker.
Could you please submit a reduced test case on jsFiddle.net that reproduces the issue your user is seeing?. Due to the variability of different solutions, having this would greatly assist in us chasing up the particular reported issue. Furthermore, would it be possible to find out what platform (Linux, OSX, Windows) your user was using when they incurred the bug?