Last modified: 2014-06-21 19:58:05 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T42812, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 40812 - jquery.makeCollapsible: Refactor to use CSS instead of JavaScript to do the expansion/collapse (including initial state)
jquery.makeCollapsible: Refactor to use CSS instead of JavaScript to do the e...
Status: NEW
Product: MediaWiki
Classification: Unclassified
JavaScript (Other open bugs)
1.19
All All
: Normal minor (vote)
: ---
Assigned To: Krinkle
:
: 42535 (view as bug list)
Depends on:
Blocks: 34876 40792
  Show dependency treegraph
 
Reported: 2012-10-05 21:08 UTC by Krinkle
Modified: 2014-06-21 19:58 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Krinkle 2012-10-05 21:08:21 UTC
Right now we select all state-collapsed elements when the document is ready and hide them (without animation, but still, they are hidden *after* they are first shown, no matter how short that initial show is). The problem with that is that it is a exponentially slow operation (ON).

By using CSS instead the initial state will be reflected immediately without any delay. Just like CSS "a { color: green; }" will make all anchor tags green (even anchor tags parsed after the CSS was parsed), likewise CSS like ".client-js .mw-collapsed { hidden }" will make them hidden without delay.

On top of this, we can build further and also optimise the cost of animations. Instead of animating with javascript, lets let JavaScript only toggle classes and the CSS will take care of the state and (if CSS3 is supported) make the transition animated.
Comment 1 Andre Klapper 2012-12-31 14:21:45 UTC
*** Bug 42535 has been marked as a duplicate of this bug. ***
Comment 2 Andre Klapper 2013-03-21 14:43:18 UTC
Krinkle: As this has the 1.21.0 target milestone set and you assigned this to yourself, just a reminder that this would require a patch in the next weeks, as a 1.21.0 tarball is vaguely planned for May 2013.
Comment 3 Mark A. Hershberger 2014-06-21 19:58:05 UTC
Removing target milestone that was in the past.

If you want this in a specific release, have a good reason AND you are willing to find resources to fix this bug, feel free to change it to something appropriate.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links