Side navigation
#8629 closed bug (worksforme)
Opened March 25, 2011 12:20AM UTC
Closed April 17, 2011 08:52PM UTC
Last modified April 30, 2011 12:30PM UTC
fadeIn for a table row does not remove display: block
Reported by: | jostster | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | effects | Version: | 1.5.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
This is a duplicate of http://bugs.jquery.com/ticket/2185 but still is not fixed in 1.5.1. I have a table row with the only style being
<tr style="border: thin solid lightgrey;"></tr>
I then clone that row and do a fadeIn but it adds display: block to the end so it looks like this
<tr style="border: thin solid lightgrey; display: block;"></tr>
In firefox this makes the table row look EXTREMELY ugly. In safari it looks normal.
I have created a JSFiddle page with parts of the table and jquery source code to duplicate the issue
Attachments (0)
Change History (10)
Changed March 25, 2011 12:22AM UTC by comment:1
Changed March 30, 2011 04:30PM UTC by comment:2
owner: | → jostster |
---|---|
status: | new → pending |
Can you create a reduced test case? Your test case is too complex to clearly demonstrate a bug in core.
Changed March 30, 2011 04:47PM UTC by comment:3
Here's a simplified test case that shows that the faded-in TR gets display: block in Firefox 2-4.
Changed March 30, 2011 04:48PM UTC by comment:4
component: | unfiled → effects |
---|---|
milestone: | 1.next → 1.6 |
owner: | jostster |
priority: | undecided → blocker |
status: | pending → new |
Changed March 30, 2011 07:16PM UTC by comment:5
status: | new → open |
---|
Changed March 31, 2011 06:26PM UTC by comment:6
Ty cowboy for the test case
Changed April 17, 2011 08:52PM UTC by comment:7
milestone: | 1.6 |
---|---|
priority: | blocker → low |
resolution: | → worksforme |
status: | open → closed |
The fix for this ends up being rather easy: Just .hide() the element after you insert it into the page:
Changed April 21, 2011 05:40PM UTC by comment:8
_comment0: | Providing a work around shouldn't be a permanent fix... → 1303407666197751 |
---|
Changed April 21, 2011 05:40PM UTC by comment:9
Replying to [comment:7 john]:
The fix for this ends up being rather easy: Just .hide() the element after you insert it into the page: http://jsfiddle.net/DzH9x/5/
Providing a work around shouldn't be a permanent fix...
Changed April 30, 2011 12:30PM UTC by comment:10
A perm fix would be nice john
I forgot to mention in the last table row for each section click the + sign to duplicate this issue.