mediawiki-skins-Vector/includes/templates/TableOfContentsContainer.mustache

{{#data-toc}}
<nav id="mw-panel-toc" role="navigation" aria-label="{{ msg-vector-toc-label }}" data-event-name="ui.sidebar-toc" class="mw-table-of-contents-container">
	{{! T313060 Additional container div needed to prevent the sticky element from being siblings with the footer }}
	{{>PinnableContainer/Pinned/Open}}
		{{#is-pinned}}{{>TableOfContents}}{{/is-pinned}}
	{{>PinnableContainer/Close}}
</nav>
{{/data-toc}}
Replace .sidebar-toc class with .vector-toc and use PinnableElement in TOC Using PinnableElement in the TOC allows us to reuse styles associated with all PinnableElements, and helps ensure consistency between page tools and the TOC. This is something that would probably need to be done for T324505 anyway Rather than updating PinnableElement to accept a class prop, I chose to rename '.sidebar-toc' to '.vector-toc', making the TOC's naming conventions consistent with the rest of Vector. "sidebar" doesn't make sense anymore anyway, as the TOC can be in multiple locations and it's best to avoid the "sidebar" term Bug: T324877 Change-Id: I5b9228380f5c4674ef424d33127a5cb4010822da 2022-12-20 22:58:44 +00:00			`{{#data-toc}}`
			`<nav id="mw-panel-toc" role="navigation" aria-label="{{ msg-vector-toc-label }}" data-event-name="ui.sidebar-toc" class="mw-table-of-contents-container">`
Create new sticky toc container Bug: T313060 Change-Id: Ia263c606dce5a6060b6b29fbaedc49cef3e17a5c 2022-08-24 18:53:37 +00:00			`{{! T313060 Additional container div needed to prevent the sticky element from being siblings with the footer }}`
Templates: Reorganize pinned containers The UnpinnedContainer and PinnedContainer are versions of the same component but with different states. Recognize them by organizing them in the same subfolder. Update all existing usages. Bug: T317900 Change-Id: I2c25937190997764fa23e0b581be5538ba4d06de 2022-12-09 23:32:43 +00:00			`{{>PinnableContainer/Pinned/Open}}`
Generalize Pinnable functionality to not be limited to dropdowns, make Pinnable templates composable This patch involves cached HTML changes - Replace '-content-container' id with '-unpinned-container' - Replace '-content' id with '-pinnable-element' - Rename pinnableHeader.js to pinnableElement.js - Replace PinnableDropdownContents.mustache with PinnableElement/Open.mustache and Close - Add PinnedContainer/Open & Close and UnpinnedContainer/Open & Close - Rename .vector-dropdown-content to .vector-pinnable-element - Add new PinnableElement.less stylesheet Bug: T318013 Change-Id: I85aec387f87126a17e760fd9fd10e10572ff3152 2022-11-28 21:08:40 +00:00			`{{#is-pinned}}{{>TableOfContents}}{{/is-pinned}}`
Templates: Reorganize pinned containers The UnpinnedContainer and PinnedContainer are versions of the same component but with different states. Recognize them by organizing them in the same subfolder. Update all existing usages. Bug: T317900 Change-Id: I2c25937190997764fa23e0b581be5538ba4d06de 2022-12-09 23:32:43 +00:00			`{{>PinnableContainer/Close}}`
Replace .sidebar-toc class with .vector-toc and use PinnableElement in TOC Using PinnableElement in the TOC allows us to reuse styles associated with all PinnableElements, and helps ensure consistency between page tools and the TOC. This is something that would probably need to be done for T324505 anyway Rather than updating PinnableElement to accept a class prop, I chose to rename '.sidebar-toc' to '.vector-toc', making the TOC's naming conventions consistent with the rest of Vector. "sidebar" doesn't make sense anymore anyway, as the TOC can be in multiple locations and it's best to avoid the "sidebar" term Bug: T324877 Change-Id: I5b9228380f5c4674ef424d33127a5cb4010822da 2022-12-20 22:58:44 +00:00			`</nav>`
			`{{/data-toc}}`