Last modified: 2009-06-13 07:48:09 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 T21071, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 19071 - CategoryTree always start fully expanded except last level
CategoryTree always start fully expanded except last level
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
CategoryTree (Other open bugs)
unspecified
All All
: Normal critical (vote)
: ---
Assigned To: Daniel Kinzler
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-03 19:40 UTC by baddress@gmail.com
Modified: 2009-06-13 07:48 UTC (History)
2 users (show)

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


Attachments

Description baddress@gmail.com 2009-06-03 19:40:42 UTC
This occur using latest CategoryTree on MediaWiki 1.14+.  

CategoryTree always start fully expanded except last level. This make CategoryTree not usable for depth > 2. Need to get back old behaviour of CategoryTree start fully collapse without regard to how many depth specified.

For example, set depth=4 means level 0-3 fully expanded and only level 4 show the + and be collapsed.

For further example, set depth=8 means level 0-7 fully expanded and only level 8 show + and be collapsed. 

This make CategoryTree unacceptable for use of depth > 2, as listing becomes too long for navigation.

Need to have the old behaviour return or alternatively a parameter can be set, for instance onload=collapse or onload=expand to determine initial display behaviour.
Comment 1 Daniel Kinzler 2009-06-13 07:48:09 UTC
I don't understand - if you don't want it to expand on load, what would the depth parameter be good for? just remove it. 

depth "determines how many levels of the tree are shown initially" (from the manual page). This was always the case, as long as that option existed.

closing.

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


Navigation
Links