UI Component library
Search input
find items in a collection of data
How it works
Single searches allow the user the quickly search a collection of data. A search is input in the search field and the results are shown immediately (using JS) or after the search has been posted to Moodle.
Searches are used in the page navbar, blocks, module pages, settings, the contentbank etc.
Example
core/search_input
core/search_input
Use
Use a default search input when searching is not expected to be the primary action on this page. Use the emphasized search when it is the default action AND the only search input found on the page. (except the navbar search).
Variables
- action: used to specify the form (get) action
- extraclasses: add these css classes to the search wrapper
- uniqid: Unique string
- inputname: form field name for search input
- inform: search is part of a larger form
- query: current search value from user input
- btnclass: use a btn class for the btn design, (btn-secondary, btn-primary)
- searchstring: string describing current search for placeholder and aria-label
- hiddenfields: array with name valua pairs for extra hidden form fields
Auto search input with clear option
core/search_input_auto
Use
This search option is used when the search imput immediately triggers updating data displayed below the search, for example: a table of usernames. It includes a clear button that clears the input on typeing.
Variables
- uniqid: Unique string
- placeholder: search placeholder
Navbar search form
core/search_input_navbar
Use
This search should be used once on the page and triggers a global site search. It uses a minimal amount of space to prevent breakage on mobile use.
Features
- click search button to start typing
- click close button to hide search
- click enter after input to post the form
- uses very little space
- overlaps navbar when viewed on mobile.