Opened 12 years ago
Closed 12 years ago
#9336 closed enhancement (wontfix)
:hidden doesn't check for opacity: 0
Reported by: | lonesomeday | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | 1.7 |
Component: | effects | Version: | 1.6.1 |
Keywords: | needsreview, 1.7-discuss | Cc: | |
Blocked by: | Blocking: |
Description (last modified by )
The logical way to prepare an element to be faded in using fadeIn
is by setting the opacity style to 0. However, invoking is(':hidden')
on an element with opacity 0 returns false, unless hidden by display: none
.
It would be useful if the :hidden
filter checked the opacity setting.
Change History (12)
comment:1 Changed 12 years ago by
Component: | unfiled → effects |
---|---|
Keywords: | needsreview added |
Status: | new → open |
comment:4 Changed 12 years ago by
-1, It's exactly as documented. The element takes space and should be considered hidden.
comment:6 Changed 12 years ago by
Description: | modified (diff) |
---|
-1, that'd be more of an :invisible as the element still takes up space, just like with visibility:hidden
The dimensions == 0 check is expected by users nowadays.
comment:7 Changed 12 years ago by
-1, If we do opacity:0
then what about top:-10000px;left:-10000px
as well? I don't think we can change the standard to visible to human eyeballs and the docs are already clear on what we mean.
comment:8 Changed 12 years ago by
I understand the reasoning for not having it as part of the hidden
filter. Is there an argument for adding the check to the fadeIn
/fadeOut
/fadeToggle
methods instead? That's the main utility I see this as having.
comment:12 Changed 12 years ago by
Milestone: | 1.next → 1.7 |
---|---|
Priority: | undecided → low |
Resolution: | → wontfix |
Status: | open → closed |
Closing per 1.7 roadmap meeting resolution
Technically, this is all correct - but I see the conundrum. Marking "needsreview" for further bike-shedding.