activePhoneNumberType | public | | | Type of phone number, derived from textbox value. Enum with values:
-‘fixed-line’
-‘fixed-line-or-mobile’
-‘mobile’
-‘pager’
-‘personal-number’
-‘premium-rate’
-‘shared-cost’
-‘toll-free’
-‘uan’
-‘voip’
-‘unknown’
See https://www.npmjs.com/package/awesome-phonenumber | LionInputTel |
activeRegion | public | string | | Currently active region based on:
1. allowed regions: get the region from configured allowed regions (if one entry)
2. user input: try to derive active region from user input
3. locale: try to get the region from locale (`html[lang]` attribute) | LionInputTel |
allowedRegions | public | RegionCode[] | [] | The regions that should be considered when international phone numbers are detected.
(when not configured, all regions worldwide will be considered) | LionInputTel |
autocomplete | public | string | 'tel' | | LionInputTel |
fieldName | public | | | Set a default name for this field, so that validation feedback will be always
accessible and linguistically correct | LionInputTel |
formatCountryCodeStyle | public | string | 'default' | Extra styling of the format strategy
default | parentheses | LionInputTel |
formatStrategy | public | PhoneNumberFormat | 'international' | Determines what the formatter output should look like.
Formatting strategies as provided by google-libphonenumber
See: https://www.npmjs.com/package/google-libphonenumber | LionInputTel |
placeholder | public | string | '' | | LionInput |
preferredRegions | public | RegionCode[] | [] | Regions that will be shown on top of the dropdown | LionInputTel |
readOnly | public | boolean | false | A Boolean attribute which, if present, indicates that the user should not be able to edit
the value of the input. The difference between disabled and readonly is that read-only
controls can still function, whereas disabled controls generally do not function as
controls until they are enabled.
(From: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly) | LionInput |
refs | public | object | { /** @type {DropdownRef} */ dropdown: /** @type {DropdownRef} */ (createRef()), } | | |
slots | public | | | | LionInput |
type | public | string | 'text' | | LionInput |
_allCountriesLabel | protected | string | '' | Group label for all countries, when preferredCountries are shown | |
_allowedOrAllRegions | protected | RegionCode[] | | Used for rendering the region/country list | LionInputTel |
_feedbackConditionMeta | protected | | | | LionField |
_focusableNode | protected | | | | LionField |
_inputNode | protected | HTMLInputElement | | | LionInput |
_langIso | protected | RegionCode | undefined | undefined | | LionInputTel |
_phoneUtil | protected | AwesomePhoneNumber|null | | | LionInputTel |
_phoneUtilLoadComplete | protected | Promise<PhoneNumber> | | | LionInputTel |
_preferredCountriesLabel | protected | string | '' | Group label for preferred countries, when preferredCountries are shown | |
_templateDataDropdown | protected | TemplateDataForDropdownInputTel | | This method provides a TemplateData object to be fed to pure template functions, a.k.a.
Pure Templates™. The goal is to totally decouple presentation from logic here, so that
Subclassers can override all content without having to loose private info contained
within the template function that was overridden.
Subclassers would need to make sure all the contents of the TemplateData object are implemented
by making sure they are coupled to the right ‘ref’ ([data-ref=dropdown] in this example),
with the help of lit’s spread operator directive.
To enhance this process, the TemplateData object is completely typed. Ideally, this would be
enhanced by providing linters that make sure all of their required members are implemented by
a Subclasser.
When a Subclasser wants to add more data, this can be done via: | |