{{!
	string|null searchHeaderAttrsHTML
	string|null searchInputLabel
	string searchActionURL
	string searchDivID
	string|null searchInputHTML
	string|null titleHTML
	string|null fallbackSearchButtonHTML
	string|null searchButtonHTML
}}
<div id="p-search" role="search">
	<h3 {{{searchHeaderAttrsHTML}}}>
		<label for="searchInput">{{searchInputLabel}}</label>
	</h3>
	<form action="{{searchActionURL}}" id="searchform">
		<div id="{{searchDivID}}">
			{{{searchInputHTML}}}
			{{{titleHTML}}}
			{{!	We construct two buttons (for 'go' and 'fulltext' search modes), but only one will be
					visible and actionable at a time (they are overlaid on top of each other in CSS).
					* Browsers will use the 'fulltext' one by default (as it's the first in tree-order),
						which is desirable when they are unable to show search suggestions (either due to being
						broken or having JavaScript turned off).
					* The mediawiki.searchSuggest module, after doing tests for the broken browsers, removes
						the 'fulltext' button and handles 'fulltext' search itself; this will reveal the 'go'
						button and cause it to be used.	!}}
			{{{fallbackSearchButtonHTML}}}
			{{{searchButtonHTML}}}
		</div>
	</form>
</div>