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

{{!
	See @typedef MenuDefinition
}}

<div id="{{id}}" class="vector-menu{{#class}} {{.}}{{/class}}" {{{html-tooltip}}} {{{html-user-language-attributes}}}>
	{{#label}}
	<div class="vector-menu-heading{{#label-class}} {{.}}{{/label-class}}">
		{{{.}}}
	</div>
	{{/label}}
	<div class="vector-menu-content">
		{{{html-before-portal}}}
		<ul class="vector-menu-content-list">{{{html-items}}}</ul>
		{{{html-after-portal}}}
	</div>
</div>
Extract PersonalMenu,mustache component from VectorTemplate PersonalMenu is the login/logout notifications etc. menu at the very top of the Vector skin. Bug: T239248, T240062 Change-Id: Iae224cbd838e44669a9f27e6dd303c6c3b402d41 2020-01-09 10:59:09 +00:00			`{{!`
Refactor: VectorMenu merged in to Menu Bug: T249372 Change-Id: Ifaf78b507c12aa251228213c89751cbb4d111d9a 2020-05-06 00:00:56 +00:00			`See @typedef MenuDefinition`
Extract PersonalMenu,mustache component from VectorTemplate PersonalMenu is the login/logout notifications etc. menu at the very top of the Vector skin. Bug: T239248, T240062 Change-Id: Iae224cbd838e44669a9f27e6dd303c6c3b402d41 2020-01-09 10:59:09 +00:00			`}}`
Remove nav element from Vector menus and only render label elements in Vector menus when needed. Add new nav landmarks corresponding to user links, main site nav, and article editing tools. Split out legacy Menu template. Bug: T291304 Bug: T301051 Change-Id: I35c20103e4b45139ef1d3f73c23f6a744aa87a3c 2022-04-18 20:10:12 +00:00
Move Vector menu class logic into Menu mustache template Cleaned 'vector-menu' in SkinVector file, updated includes/templates/Menu.mustache and includes/templates/legacy/Menu.mustache. Bug: T290281 Change-Id: I7286fa82abfd437a228b9ac07ac781210d7cd98f 2022-05-04 22:20:23 +00:00			`<div id="{{id}}" class="vector-menu{{#class}} {{.}}{{/class}}" {{{html-tooltip}}} {{{html-user-language-attributes}}}>`
[Technical] Split up Menu.template, restrict decoratePortletData to legacy Vector Changes: * Code is moved from SkinVector to SkinVectorLegacy verbatim since it is now only needed by SkinVectorLegacy so we remove it: This step broke MainMenu rendering so this was captured in VectorComponentMainMenu The isLegacy code no longer makes sense and is removed in a follow up * storybook no longer run on CI Authors: Bernard Wang and Jon Robson Bug: T321102 Bug: T319349 Change-Id: Ib424ca1c767161fdae8c0aeedfe662b7fa039ff6 2022-10-27 23:52:23 +00:00			`{{#label}}`
			`<div class="vector-menu-heading{{#label-class}} {{.}}{{/label-class}}">`
			`{{{.}}}`
Remove gradient from modern Vector, align SidebarAction with portlet styles and classes Bug: T307771 Change-Id: I92fd11b89d4afbf99dd7ab51990835b9754767a1 2022-08-12 16:11:41 +00:00			`</div>`
[Technical] Split up Menu.template, restrict decoratePortletData to legacy Vector Changes: * Code is moved from SkinVector to SkinVectorLegacy verbatim since it is now only needed by SkinVectorLegacy so we remove it: This step broke MainMenu rendering so this was captured in VectorComponentMainMenu The isLegacy code no longer makes sense and is removed in a follow up * storybook no longer run on CI Authors: Bernard Wang and Jon Robson Bug: T321102 Bug: T319349 Change-Id: Ib424ca1c767161fdae8c0aeedfe662b7fa039ff6 2022-10-27 23:52:23 +00:00			`{{/label}}`
Drop unsupported skin CSS classes Drop support for vectorMenu, vectorTabs and vectorMenuCheckbox, body, menu selectors in preference for standard selectors. This change will impact a large amount of user scripts/styles but should not impact any gadgets. These classes were kept around for user scripts and styles however are not needed internally. As we transition to a more maintainable skin menu system, it is time to lose these selectors even though this will cause disruption. Vector now will use the mw-portlet class rather than the vector-menu class in its own CSS styling, however it keeps the other classes to allow differentiation of the different types of menu. Changes to test: Previously the tests assumed all portlets were empty when checking the classes. This is very rare, so its better to check the classes of non-empty portlets, so several tests are updated accordingly to drop the emptyPortlet class. Bug: T262092 Change-Id: I1824335eb47d613c2a4804ec1f1106c0f4c16101 2020-09-04 19:34:05 +00:00			`<div class="vector-menu-content">`
Remove UserMenu and use Menu template instead - Adds html-before-portlet to Menu.mustache - Removes UserMenu.mustache and type def - Factors out getCreateAccountHTML and getLoginHTML for generating HTML used in Menu - Scopes UserLink template data under "data-vector-user-links" Follow up to: 298f945983 Bug: T284584 Change-Id: I91104eb7c4fd12756e770561666f4c9a64da57d6 2021-06-03 21:37:01 +00:00			`{{{html-before-portal}}}`
Drop unsupported skin CSS classes Drop support for vectorMenu, vectorTabs and vectorMenuCheckbox, body, menu selectors in preference for standard selectors. This change will impact a large amount of user scripts/styles but should not impact any gadgets. These classes were kept around for user scripts and styles however are not needed internally. As we transition to a more maintainable skin menu system, it is time to lose these selectors even though this will cause disruption. Vector now will use the mw-portlet class rather than the vector-menu class in its own CSS styling, however it keeps the other classes to allow differentiation of the different types of menu. Changes to test: Previously the tests assumed all portlets were empty when checking the classes. This is very rare, so its better to check the classes of non-empty portlets, so several tests are updated accordingly to drop the emptyPortlet class. Bug: T262092 Change-Id: I1824335eb47d613c2a4804ec1f1106c0f4c16101 2020-09-04 19:34:05 +00:00			`<ul class="vector-menu-content-list">{{{html-items}}}</ul>`
Refactor: Portal is also a Menu To complete the refactor, the Portal is also refactored as a Menu using the getMenu function. An old code path supporting portals outputted by hooks with strings is marked as deprecated to simplify this code in future. array-portals-first -> data-portals-first (the value is not an array) Changes: * $this->getLanguages and $this->getToolbox() always returns an array (see BaseTemplate) but we previously supported portals made using raw HTML. Let's move away from that behaviour and deprecate it. * Hooks are moved into buildSidebarProps and marked as deprecated where possible (SkinTemplateToolboxEnd). SidebarBeforeOutput can be used instead. Bug: T249372 Change-Id: I2549af3e24e5d51c09e9a88ca50a0d9b2e154c3f 2020-04-07 23:21:20 +00:00			`{{{html-after-portal}}}`
			`</div>`
Remove nav element from Vector menus and only render label elements in Vector menus when needed. Add new nav landmarks corresponding to user links, main site nav, and article editing tools. Split out legacy Menu template. Bug: T291304 Bug: T301051 Change-Id: I35c20103e4b45139ef1d3f73c23f6a744aa87a3c 2022-04-18 20:10:12 +00:00			`</div>`