Side navigation
#4741 closed bug (wontfix)
Opened June 09, 2009 02:16PM UTC
Closed April 01, 2011 02:35AM UTC
Last modified April 01, 2011 02:35AM UTC
Toggle Performance Decreased for Tables
| Reported by: | JonBrunt | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | effects | Version: | 1.4.4rc |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
The performance of the toggle command has slowed down quite a bit since upgrading from 1.3.1 to 1.3.2 when applied to columns in a table. The effect becomes much more pronounced as the size of the table grows. I've tested this out in FF3, IE6 and IE7.
I've included two sample pages with one using 1.3.1 and 1.3.2 to illustrate the difference.
Attachments (2)
Change History (4)
Changed June 13, 2010 02:56AM UTC by comment:1
| component: | unfiled → fx |
|---|
Changed October 31, 2010 09:52PM UTC by comment:2
| keywords: | toggle table performance → toggle table performance needsreview |
|---|---|
| milestone: | 1.3.2 |
| priority: | major → low |
| version: | 1.3.2 → 1.4.4rc |
22ms in 1.3.1; 133ms in 1.3.2+ (including 1.4.4rc1). Not sure if there is actually anything we can do to speed this back up again since I would guess the slowness is due to additional required checks.
Changed April 01, 2011 02:35AM UTC by comment:3
| resolution: | → wontfix |
|---|---|
| status: | new → closed |
I don't see this as a common case. It would be better to optimize this case in the page. If you need to toggle all rows, toggle the table. If you need to toggle known *groups* of rows, consider putting them into separate tbodies.
Changed April 01, 2011 02:35AM UTC by comment:4
| keywords: | toggle table performance needsreview |
|---|