#11036 closed bug (invalid)
.slideToggle() not working properly in fieldset tags in Firefox
Reported by: | leobalter | Owned by: | leobalter |
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.7.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
http://jsbin.com/upajes/2/edit#javascript,html
When I call .slideToggle() in fieldset tags the element goes to display none, but its contents keep visible.
It looks like a firefox bug too, as Chrome and Opera are ok.
If I change the fieldset to other element, slideToggle will work.
Tested in Firefox 8 up to 10 (Nightly).
Change History (4)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Owner: | set to leobalter |
---|---|
Status: | new → pending |
Do you have a cross-ref to a Bugzilla bug for this? It really should be fixed there.
comment:3 Changed 11 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!
comment:4 Changed 10 years ago by
In Firefox 22 (Mac), there is a different effect: The contents are visible during the animation and overflow the element. Everything is normal before and after the animation. It is possible to work around this by creating a div around the fieldset and calling one of the slide methods on that.
Interesting, I'm not sure if this is a bug in jQuery or Firefox. It appears to be a bug in Firefox. With firebug you can see that the element is set to display: none but its children are still showing. If you hover over any of the elements in firebug it forces a rerender and the rendering is fixed (elements are hidden).
So it seems like something in firefox, but we might be able to find a workaround.