Porsche Design System
You are currently viewing an earlier release of the Porsche Design System.Switch to the latest Porsche Design System documentation.
SearchNavigate to GitHub repository of Porsche Design SystemOpen sidebar
ConfiguratorExamplesUsageAccessibilityAPI
Input Search Table of Contents Usage The following section provides guidance for designers and developers on how to use this component in different situations. Do: Use when a keyword or key value for a search request is necessary. Use without a label only when the context is clear. Use with a slotted locate button when a locate action can be performed. Use a loading state to indicate a search is being performed. Use an asterisk to indicate required fields. Use success or error messages if the user input was inappropriate. Use search suggestions or recent history when it adds contextual value. Don't: Don’t use labels with more than two words whenever possible (keep them short and descriptive). Don’t use instructional or descriptive text as the label. Don’t use p-input-search for purposes other than search. Don’t use compact variants in marketing applications. Don’t manipulate or replace the default search icon. Related Components Input Date Input Email Input Month Input Number Input Password Input Tel Input Text Input Time Input Url Input Week
Global settingsColor SchemeAll color tokens use the light-dark() CSS function. Set the theme via the CSS color-scheme property: light for light mode, dark for dark mode, or light dark to follow the user's system preference.LightDarkLight DarkDirectionThe dir global attribute in HTML changes the direction of text and other content within an element. It's most often used on the <html> tag to set the entire page's direction, which is crucial for supporting languages that are written from right to left (RTL), such as Arabic and Hebrew. For example, using <html dir="rtl"> makes the entire page display from right to left, adjusting the layout and text flow accordingly.LTR (left-to-right)RTL (right-to-left)Text ZoomTo ensure accessibility and comply with WCAG 2.2 AA standards, it is mandatory for web content to support text resizing up to at least 200% without loss of content or functionality. Using relative units like rem is a best practice for achieving this, as they allow the text to scale uniformly based on the user's browser settings.100%130%150%200%