Save wiki expander state

[anonymous]

Replying to Christian Boos:

As for the expander, … the possibility to save as a UI preference the initial state of the wiki page, expanded or constrained.

[anonymous]

+1

Constrained completely breaks many existing wiki pages that contain large macros (​th:WikiExtras boxes, calendars, kanban boards, …)

[anonymous]

Can it be easily disabled or changed to default to expanded?

[Christian Boos]

Yes, it's been implemented (r15524).

For calendars, kanban boards, and other generated content that would be better always presented unconstrained even in narrow mode and is not already automatically detected as such (like big tables and images are), we could perhaps add a .fullwidth class to that effect.

Could you point me to some (simple) example, perhaps the calendar one?

[Ryan J Ollos]

And can be seen in action here, prefs/userinterface.

[anonymous]

Thank you guys for the pointers!

​th:WikiExtrasPlugin Example:

{{{#!rbox width=30em
[[TicketQuery(status!=closed,keywords=right)]]
}}}
{{{#!box align=left width=30em
[[TicketQuery(status!=closed,keywords=left)]]
}}}
{{{#!box
[[TicketQuery(status!=closed,keywords=center)]]
}}}

In constrained view the boxes are stacked above each other instead of left / center / right.

The other examples (​th:WeekPlanPlugin calendar etc.) do overflow the constrained page.

[Ryan J Ollos]

Milestone renamed