Side navigation
#11017 closed bug (invalid)
Opened December 13, 2011 08:17PM UTC
Closed December 28, 2011 08:02AM UTC
slideDown() on Internet Explorer requires "hasLayout"
| Reported by: | boydb@midnightdesign.ws | Owned by: | boydb@midnightdesign.ws |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.6.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
Due to the way that IE renders items, using slideDown() on a DOM element that does not have the "hasLayout" internal setting does not display correctly. It slides down, but after it is fully-extended, the contents are immediately made invisible. It is still a block element (if it is a block element by default) and moves the rest of the content down the page, and subsequent javascript calls will report the "display" attribute is not "none", but all content is invisible.
This effect can be remedied by giving the sliding element a "zoom:1" CSS attribute. Currently that can be done just in the HTML of the page, though it would be most seamless if jQuery did this as part of the slideDown() effect, if the browser was ID and the zoom attribute was not already set.
Attachments (0)
Change History (2)
Changed December 14, 2011 12:11AM UTC by comment:1
| owner: | → boydb@midnightdesign.ws |
|---|---|
| status: | new → pending |
Changed December 28, 2011 08:02AM UTC by comment:2
| 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.