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

{{!
 See @typedef SearchData
}}
<div id="p-search" role="search">
	<h3 {{{html-userlangattributes}}}>
		<label for="searchInput">{{msg-search}}</label>
	</h3>
	<form action="{{form-action}}" id="searchform">
		<div id="{{form-id}}">
			{{{html-input}}}
			<input type="hidden" name="title" value="{{page-title}}">
			{{!	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.	!}}
			{{{html-button-search-fallback}}}
			{{{html-button-search}}}
		</div>
	</form>
</div>
[Hygiene] [Mustache] improve template parameters and docs Add typing expectations to search box template parameters. Add context expectations to search box and tabs templates. Bug: T239248 Change-Id: I4ff1920f5489b68ef73a219ceeceb1f5511fc9e8 2019-12-06 23:37:39 +00:00			`{{!`
Cleanup: Use consistent naming in SearchBox We have conventions about template variable naming. * Drop camel case * Prefix message keys with `msg-` followed by message key name * Prefix HTML with `html-` Change-Id: I34f04f3d217dc8caa4dcc29e60058951a6555b1e 2020-05-29 19:07:55 +00:00			`See @typedef SearchData`
[Hygiene] [Mustache] improve template parameters and docs Add typing expectations to search box template parameters. Add context expectations to search box and tabs templates. Bug: T239248 Change-Id: I4ff1920f5489b68ef73a219ceeceb1f5511fc9e8 2019-12-06 23:37:39 +00:00			`}}`
Hygiene: extract VectorTemplate inline HTML to SearchComponent Mustache file Extract SearchComponent.mustache from VectorTemplate. The "search" message is now escaped by the template parser. As is, htmlspecialchars() for "wgScript". A later patch will change each component renderer function as well as renderNavigation() to return a string. Change-Id: I3084b7e0ef73d320c85ee780c9eff13ecea92906 2019-11-20 19:43:07 +00:00			`<div id="p-search" role="search">`
Cleanup: Use consistent naming in SearchBox We have conventions about template variable naming. * Drop camel case * Prefix message keys with `msg-` followed by message key name * Prefix HTML with `html-` Change-Id: I34f04f3d217dc8caa4dcc29e60058951a6555b1e 2020-05-29 19:07:55 +00:00			`<h3 {{{html-userlangattributes}}}>`
			`<label for="searchInput">{{msg-search}}</label>`
Hygiene: extract VectorTemplate inline HTML to SearchComponent Mustache file Extract SearchComponent.mustache from VectorTemplate. The "search" message is now escaped by the template parser. As is, htmlspecialchars() for "wgScript". A later patch will change each component renderer function as well as renderNavigation() to return a string. Change-Id: I3084b7e0ef73d320c85ee780c9eff13ecea92906 2019-11-20 19:43:07 +00:00			`</h3>`
Cleanup: Use consistent naming in SearchBox We have conventions about template variable naming. * Drop camel case * Prefix message keys with `msg-` followed by message key name * Prefix HTML with `html-` Change-Id: I34f04f3d217dc8caa4dcc29e60058951a6555b1e 2020-05-29 19:07:55 +00:00			`<form action="{{form-action}}" id="searchform">`
			`<div id="{{form-id}}">`
			`{{{html-input}}}`
			`<input type="hidden" name="title" value="{{page-title}}">`
Hygiene: extract VectorTemplate inline HTML to SearchComponent Mustache file Extract SearchComponent.mustache from VectorTemplate. The "search" message is now escaped by the template parser. As is, htmlspecialchars() for "wgScript". A later patch will change each component renderer function as well as renderNavigation() to return a string. Change-Id: I3084b7e0ef73d320c85ee780c9eff13ecea92906 2019-11-20 19:43:07 +00:00			`{{! 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. !}}`
Cleanup: Use consistent naming in SearchBox We have conventions about template variable naming. * Drop camel case * Prefix message keys with `msg-` followed by message key name * Prefix HTML with `html-` Change-Id: I34f04f3d217dc8caa4dcc29e60058951a6555b1e 2020-05-29 19:07:55 +00:00			`{{{html-button-search-fallback}}}`
			`{{{html-button-search}}}`
Hygiene: extract VectorTemplate inline HTML to SearchComponent Mustache file Extract SearchComponent.mustache from VectorTemplate. The "search" message is now escaped by the template parser. As is, htmlspecialchars() for "wgScript". A later patch will change each component renderer function as well as renderNavigation() to return a string. Change-Id: I3084b7e0ef73d320c85ee780c9eff13ecea92906 2019-11-20 19:43:07 +00:00			`</div>`
			`</form>`
			`</div>`