#11218 closed bug (invalid)
.is(":hidden") on a list with 'display:inline' always true in Chrome and Safari
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.7.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Using .is() to check visibility of a list (<ul>) with a display of 'inline' seems to always believe an element is invisible in the latest Chrome and Safari. Note that .toggle() uses is(":hidden"), so .toggle() is not working for this case, either.
I've created a simple example that illustrates the problem when used in Safari or Chrome (Windows or Mac).
<html>
<head>
<style type="text/css">
.theList {
display: inline;
}
</style>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript">
$(document).ready(function () {
var theList = $(".theList");
$(".showHideButton").click(function () {
if (theList.is(":hidden")) {
theList.show();
} else {
theList.hide();
}
});
});
</script>
</head>
<body>
<input type="button" class="showHideButton" value="Toggle the message" />
<ul class="theList">
<li>Peek</li>
<li>a</li>
<li>boo!</li>
</ul>
</body>
</html>
Change History (2)
comment:1 Changed 10 years ago by
| Owner: | set to ac@… |
|---|---|
| Status: | new → pending |
comment:2 Changed 9 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | pending → closed |
Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!
Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.
Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: http://jsfiddle.net/FrKyN/ Open the link and click to "Fork" (in the top menu) to get started.