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

<header class="vector-header mw-header">
	<div class="vector-header-start">
		<nav class="vector-main-menu-landmark" aria-label="{{msg-vector-site-nav-label}}" role="navigation">
			{{>MainMenuDropdown}}
		</nav>
		{{#data-logos}}{{>Logo}}{{/data-logos}}
	</div>
	<div class="vector-header-end">
		{{#data-search-box}}{{>SearchBox}}{{/data-search-box}}
		{{#data-vector-user-links}}{{>UserLinks}}{{/data-vector-user-links}}
	</div>
</header>
Implement new zebra design for the header under the flag Bug: T332449 Depends-On: Ia21c14f72631e607e0d626408557eacb83529a03 Change-Id: I9a7d6fac7c44be1983281a44766d34a16f515b40 2023-03-31 19:25:09 +00:00			`<header class="vector-header mw-header">`
Remove CSS classes and selectors from cached HTML Bug: T316570 Depends-on: Ib4050768f20b1734d356104f18aa539f657099d8 Change-Id: I97f87b32402d7f4fd790f9a8b9abab42efd9d890 2022-10-17 21:27:57 +00:00			`<div class="vector-header-start">`
remove Page Tools config & HTML Removes the config option for Page Tool menu, its associated logic, along with the associated HTML from the mustache templates. Hardcodes the `vector-feature-page-tools-enabled` class into the HTML element to prevent breakage. Bug: T332090 Change-Id: I6466d80c6970bcc8e28d897b6bdff911a90e3655 2023-03-27 20:29:34 +00:00			`<nav class="vector-main-menu-landmark" aria-label="{{msg-vector-site-nav-label}}" role="navigation">`
			`{{>MainMenuDropdown}}`
			`</nav>`
Replace incorrectly mw- prefixed classes Rename template and CSS files to match updated naming conventions, replaces instances of "sidebar" with "main menu" Bug: T316570 Bug: T317437 Change-Id: Ib4050768f20b1734d356104f18aa539f657099d8 2022-10-17 20:09:53 +00:00			`{{#data-logos}}{{>Logo}}{{/data-logos}}`
[Grid preparation] Structure the header Restructure the header to have two child elements Change-Id: Ib5b7f31419ae6b62f62878947651b8ab843a3955 2022-05-04 22:20:23 +00:00			`</div>`
Remove CSS classes and selectors from cached HTML Bug: T316570 Depends-on: Ib4050768f20b1734d356104f18aa539f657099d8 Change-Id: I97f87b32402d7f4fd790f9a8b9abab42efd9d890 2022-10-17 21:27:57 +00:00			`<div class="vector-header-end">`
Replace incorrectly mw- prefixed classes Rename template and CSS files to match updated naming conventions, replaces instances of "sidebar" with "main menu" Bug: T316570 Bug: T317437 Change-Id: Ib4050768f20b1734d356104f18aa539f657099d8 2022-10-17 20:09:53 +00:00			`{{#data-search-box}}{{>SearchBox}}{{/data-search-box}}`
			`{{#data-vector-user-links}}{{>UserLinks}}{{/data-vector-user-links}}`
[Grid preparation] Structure the header Restructure the header to have two child elements Change-Id: Ib5b7f31419ae6b62f62878947651b8ab843a3955 2022-05-04 22:20:23 +00:00			`</div>`
Switch to navigation-first DOM order under `$wgVectorIsSearchInHeader` feature flag This moves the header, navigation, sidebar, and article toolbar to be before the content in the DOM. As a result, a lot of absolute positioning logic can be removed and styles can be simplified. Note that although the sidebar was moved from the header into the workspace container allowing it to de-absolutely positioned, its absolute positioning was kept intact as it has a fair amount of complexity that should be handled in a separate task. To activate, set `$wgVectorIsSearchInHeader = true;` Changes that could cause concern: * The "jump to search" link was removed as the search is now much earlier in the DOM and I questioned the value of keeping this. However, it can be added back in if this change is contentious. * A "jump to content" link was added to account for the new DOM order. * Because the sidebar was taken out of the header, users will not be able to tab from the sidebar button into the sidebar without additional tweaking (e.g. should we add JS to enable this?). It was deemed that this work can be saved as a follow-up task. * I applied `overflow-y: auto` to the `mw-page-container` because the header's top margin was collapsing and caused whitespace to appear between the viewport and the header. Alternatively, we could apply a top padding to the page container and remove the header's top margin. I went for the simplest solution but am open to alternatives. * I left the footer as-is in this patch to minimize risk. It might be cleaner later on to move the footer inside the workspace container which would leave only one workspace container. Bug: T261802 Change-Id: Ic553fab3bde25769b103d899b92b3b694c00c384 2020-09-08 23:20:58 +00:00			`</header>`