Side navigation
#7947 closed bug (fixed)
Opened January 11, 2011 04:20PM UTC
Closed January 12, 2011 04:45PM UTC
Buggy Animation when Unhiding Colspanned Table Row
| Reported by: | Tomasz Trejderowski <tomasz@trejderowski.pl> | Owned by: | Tomasz Trejderowski <tomasz@trejderowski.pl> |
|---|---|---|---|
| Priority: | low | Milestone: | 1.4.3 |
| Component: | effects | Version: | 1.4.2 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
When you hide (using style for example - display: none) a table cell that is colspanned to fit more cells in upper row, then the only option to unhide this table row is to resign from using animations (i.e. use toggle() or show() without params).
If you use animate() or toggle() or show() with animation the overall effects looks a bit buggy - i.e. you clearly see that not colspanned cell is animated and only after animation ends it is being colspanned. Producing rather not acceptable visual effects.
I don't know if this is a bug or wanted effect and therfore - if this can be fixed?
Attachments (0)
Change History (3)
Changed January 12, 2011 12:33AM UTC by comment:1
| owner: | → Tomasz Trejderowski <tomasz@trejderowski.pl> |
|---|---|
| status: | new → pending |
Changed January 12, 2011 08:13AM UTC by comment:2
| status: | pending → new |
|---|
Hello,
Test case has been created:
However, it turned out that this bug has already been solved in jQuery 1.4.3, therefore it affects only version 1.4.2 and below. I haven't noticed earlier that my outdated framework version ships with outdated version of jQuery! :]
Please forgive me for not testing this out earlier and please, close this ticket. Thank you.
Changed January 12, 2011 04:45PM UTC by comment:3
| component: | unfiled → effects |
|---|---|
| milestone: | 1.next → 1.4.3 |
| priority: | undecided → low |
| resolution: | → fixed |
| status: | new → closed |
| version: | 1.4.4 → 1.4.2 |
Closing per request of the reporter. Fixed in 1.4.3
Thanks for submitting a ticket to the jQuery Bug Tracker! Could you kindly also submit a reduced test case that reproduces the issue you are experiencing on http://jsfiddle.net so we can evaluate and test it further?