Problem about tree structure of a page

[zkosk]

In the page "Perturbation_theory_(quantum_mechanics)", some subtree are put at the same level as their parent:

"Generalization to multi-parameter case" is the parent node, all the others in the picture are its child nodes. But they are not hidden then the parent is collapsed. Not sure whether it is a problem of online Wiki or the offliner tool.

maxi Version "6,134,097 articles in English"

[kelson42]

I confirm the bug, look at http://library.kiwix.org/wikipedia_en_all_maxi/A/Perturbation_theory_(quantum_mechanics).

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.

[MananJethwani]

@kelson42 the current implementation for tree structure considers dropdown structure to be followed only for the first level, and puts all others on the same level, as far as I remember this was discussed in some other issue as well, do you want me to implement a proper method that might use recursion or stack to implement a proper tree structure. or the current method should be kept?

[kelson42]

@MananJethwani I really wonder about that. Sounds kind of "crazy". Obviously it has to manage an indefinite level of depth.

[the-illuminatus]

is the issue still open?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions.

[kelson42]

Wondering if this makes sense to implement this just before #1664?!

[Jaifroid]

Personally I'd agree that #1664 is higher priority, and it's possible it could make this issue redundant. But we won't know that till the new endpoint has been implemented.

[kelson42]

Lets implement #1664 first

[teraspora]

@zkosk @kelson42 In Chrome Version 126.0.6478.182 (Official Build) (64-bit) and Firefox 128.0 (64-bit) I don't see the arrows on either the parent or child nodes: the content is not collapsible.

So it would appear that this is not now an issue.

However, if it still occurs in some browser then can you provide a link to example content and browser name/version? Then I will be happy to have a look at it. Else should this issue be closed?