@lion/ui 0.7.6 → 0.7.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (135) hide show
  1. package/README.md +1 -2
  2. package/components/button/test-suites/LionButton.suite.js +3 -1
  3. package/components/calendar/src/LionCalendar.js +9 -5
  4. package/components/calendar/test/lion-calendar.test.js +33 -6
  5. package/components/combobox/src/LionCombobox.js +33 -9
  6. package/components/combobox/test/lion-combobox.test.js +134 -7
  7. package/components/dialog/test/lion-dialog.test.js +59 -1
  8. package/components/input-datepicker/src/LionInputDatepicker.js +1 -21
  9. package/components/input-datepicker/test/lion-input-datepicker.test.js +30 -3
  10. package/components/input-file/src/FileHandle.js +1 -1
  11. package/components/input-file/src/LionInputFile.js +1 -3
  12. package/components/input-file/test/lion-input-file.test.js +11 -14
  13. package/components/overlays/src/OverlayController.js +13 -7
  14. package/components/overlays/src/OverlayMixin.js +5 -1
  15. package/components/overlays/test/OverlayController.test.js +46 -0
  16. package/components/select-rich/src/LionSelectRich.js +12 -0
  17. package/components/select-rich/test/lion-select-rich.test.js +26 -0
  18. package/custom-elements.json +60 -73
  19. package/dist-types/components/button/test-suites/LionButton.suite.d.ts.map +1 -1
  20. package/dist-types/components/calendar/src/LionCalendar.d.ts +1 -0
  21. package/dist-types/components/calendar/src/LionCalendar.d.ts.map +1 -1
  22. package/dist-types/components/combobox/src/LionCombobox.d.ts +9 -0
  23. package/dist-types/components/combobox/src/LionCombobox.d.ts.map +1 -1
  24. package/dist-types/components/input-datepicker/src/LionInputDatepicker.d.ts +0 -5
  25. package/dist-types/components/input-datepicker/src/LionInputDatepicker.d.ts.map +1 -1
  26. package/dist-types/components/input-file/src/LionInputFile.d.ts.map +1 -1
  27. package/dist-types/components/overlays/src/OverlayController.d.ts.map +1 -1
  28. package/dist-types/components/overlays/src/OverlayMixin.d.ts.map +1 -1
  29. package/dist-types/components/select-rich/src/LionSelectRich.d.ts.map +1 -1
  30. package/dist-types/tsconfig.tsbuildinfo +1 -1
  31. package/docs/components/button/use-cases.md +2 -2
  32. package/docs/components/calendar/use-cases.md +4 -4
  33. package/docs/components/checkbox-group/api-table.md +49 -55
  34. package/docs/components/checkbox-group/overview.md +5 -5
  35. package/docs/components/checkbox-group/use-cases.md +33 -33
  36. package/docs/components/collapsible/overview.md +1 -1
  37. package/docs/components/collapsible/use-cases.md +3 -3
  38. package/docs/components/combobox/api-table.md +84 -89
  39. package/docs/components/combobox/extensions.md +20 -20
  40. package/docs/components/combobox/overview.md +1 -1
  41. package/docs/components/combobox/use-cases.md +6 -6
  42. package/docs/components/dialog/api-table.md +3 -3
  43. package/docs/components/dialog/overview.md +2 -2
  44. package/docs/components/dialog/src/external-dialog.js +32 -0
  45. package/docs/components/dialog/src/slots-dialog-content.js +1 -1
  46. package/docs/components/dialog/src/styled-dialog-content.js +1 -1
  47. package/docs/components/dialog/use-cases.md +49 -3
  48. package/docs/components/drawer/use-cases.md +3 -3
  49. package/docs/components/fieldset/api-table.md +45 -51
  50. package/docs/components/fieldset/overview.md +7 -7
  51. package/docs/components/fieldset/use-cases.md +15 -15
  52. package/docs/components/form/overview.md +7 -7
  53. package/docs/components/form/use-cases.md +4 -4
  54. package/docs/components/icon/use-cases.md +1 -1
  55. package/docs/components/input/overview.md +1 -1
  56. package/docs/components/input/use-cases.md +3 -3
  57. package/docs/components/input-amount/overview.md +3 -3
  58. package/docs/components/input-amount/use-cases.md +8 -8
  59. package/docs/components/input-date/overview.md +3 -3
  60. package/docs/components/input-date/use-cases.md +8 -8
  61. package/docs/components/input-datepicker/api-table.md +1 -3
  62. package/docs/components/input-datepicker/overview.md +5 -5
  63. package/docs/components/input-datepicker/use-cases.md +5 -5
  64. package/docs/components/input-email/overview.md +2 -2
  65. package/docs/components/input-email/use-cases.md +3 -3
  66. package/docs/components/input-file/overview.md +1 -1
  67. package/docs/components/input-iban/overview.md +2 -2
  68. package/docs/components/input-iban/use-cases.md +8 -8
  69. package/docs/components/input-range/overview.md +2 -2
  70. package/docs/components/input-stepper/api-table.md +65 -69
  71. package/docs/components/input-stepper/overview.md +1 -1
  72. package/docs/components/input-tel/overview.md +1 -1
  73. package/docs/components/input-tel/use-cases.md +9 -9
  74. package/docs/components/input-tel-dropdown/api-table.md +70 -73
  75. package/docs/components/input-tel-dropdown/extensions.md +1 -1
  76. package/docs/components/input-tel-dropdown/overview.md +1 -1
  77. package/docs/components/input-tel-dropdown/use-cases.md +5 -5
  78. package/docs/components/listbox/api-table.md +64 -70
  79. package/docs/components/listbox/overview.md +5 -5
  80. package/docs/components/listbox/use-cases.md +61 -61
  81. package/docs/components/pagination/use-cases.md +5 -5
  82. package/docs/components/radio-group/api-table.md +49 -55
  83. package/docs/components/radio-group/overview.md +6 -6
  84. package/docs/components/radio-group/use-cases.md +18 -18
  85. package/docs/components/select/use-cases.md +2 -2
  86. package/docs/components/select-rich/api-table.md +79 -85
  87. package/docs/components/select-rich/overview.md +3 -3
  88. package/docs/components/select-rich/use-cases.md +33 -33
  89. package/docs/components/steps/overview.md +4 -4
  90. package/docs/components/steps/use-cases.md +7 -7
  91. package/docs/components/tabs/examples.md +1 -1
  92. package/docs/components/tabs/use-cases.md +1 -1
  93. package/docs/components/textarea/use-cases.md +3 -3
  94. package/docs/components/tooltip/api-table.md +3 -3
  95. package/docs/components/tooltip/use-cases.md +6 -6
  96. package/docs/fundamentals/index.md +4 -4
  97. package/docs/fundamentals/node-tools/providence-analytics/LocalConfiguration.md +1 -1
  98. package/docs/fundamentals/node-tools/providence-analytics/QueryResult.md +1 -1
  99. package/docs/fundamentals/node-tools/providence-analytics/analyzer.md +1 -1
  100. package/docs/fundamentals/node-tools/providence-analytics/dashboard.md +1 -1
  101. package/docs/fundamentals/node-tools/providence-analytics/overview.md +3 -3
  102. package/docs/fundamentals/node-tools/publish-docs/overview.md +3 -3
  103. package/docs/fundamentals/node-tools/rocket-preset-extend-lion-docs/overview.md +2 -2
  104. package/docs/fundamentals/rationales/accessibility.md +1 -1
  105. package/docs/fundamentals/systems/core/SlotMixin.md +1 -1
  106. package/docs/fundamentals/systems/core/overview.md +1 -1
  107. package/docs/fundamentals/systems/form/formatting-and-parsing.md +8 -8
  108. package/docs/fundamentals/systems/form/model-value.md +1 -1
  109. package/docs/fundamentals/systems/form/overview.md +28 -28
  110. package/docs/fundamentals/systems/form/use-cases.md +19 -19
  111. package/docs/fundamentals/systems/form/validate.md +50 -50
  112. package/docs/fundamentals/systems/localize/api-table.md +10 -17
  113. package/docs/fundamentals/systems/localize/overview.md +4 -4
  114. package/docs/fundamentals/systems/localize/use-cases.md +4 -4
  115. package/docs/fundamentals/systems/overlays/_configuration-positioning.md +4 -4
  116. package/docs/fundamentals/systems/overlays/api-table.md +34 -90
  117. package/docs/fundamentals/systems/overlays/assets/umbrella-form.js +9 -9
  118. package/docs/fundamentals/systems/overlays/configuration.md +30 -30
  119. package/docs/fundamentals/systems/overlays/overview.md +6 -6
  120. package/docs/fundamentals/systems/overlays/use-cases.md +30 -30
  121. package/docs/fundamentals/tools/ajax/use-cases.md +20 -20
  122. package/docs/fundamentals/tools/helpers/action-logger.md +3 -3
  123. package/docs/fundamentals/tools/helpers/overview.md +1 -1
  124. package/docs/fundamentals/tools/singleton-manager/example-complex/demo-app.js +2 -2
  125. package/docs/fundamentals/tools/singleton-manager/example-fail/demo-app.js +2 -2
  126. package/docs/fundamentals/tools/singleton-manager/example-success/demo-app.js +2 -2
  127. package/docs/fundamentals/tools/singleton-manager/overview.md +4 -4
  128. package/docs/guides/how-to/create-a-custom-field.md +7 -7
  129. package/docs/guides/how-to/create-a-form.md +4 -4
  130. package/docs/guides/how-to/extend-a-native-input.md +2 -2
  131. package/docs/guides/index.md +8 -8
  132. package/docs/guides/principles/index.md +5 -5
  133. package/docs/guides/principles/scoped-elements.md +1 -1
  134. package/docs/guides/principles/styling.md +1 -1
  135. package/package.json +1 -1
package/docs/components/input-tel-dropdown/api-table.md CHANGED
@@ -4,79 +4,76 @@
4
4
 
5
5
  ### Fields
6
6
 
7
- | Name | Privacy | Type | Default | Description | Inherited From |
8
- | ---------------------------- | --------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
9
- | `refs` | public | `object` | `{
10
- /** @type {DropdownRef} */
11
- dropdown: /** @type {DropdownRef} */ (createRef()),
12
- }` | | |
13
- | `_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: | |
14
- | `slots` | public | | | Adds ".\_feedbackNode" as described below | LionField |
15
- | `preferredRegions` | public | `string[]` | `[]` | Regions that will be shown on top of the dropdown | |
16
- | `_allCountriesLabel` | protected | `string` | `''` | Group label for all countries, when preferredCountries are shown | |
17
- | `_preferredCountriesLabel` | protected | `string` | `''` | Group label for preferred countries, when preferredCountries are shown | |
18
- | `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 |
19
- | `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 |
20
- | `_allowedOrAllRegions` | protected | `RegionCode[]` | | Used for rendering the region/country list | LionInputTel |
21
- | `_phoneUtilLoadComplete` | protected | `Promise<PhoneNumber>` | | | LionInputTel |
22
- | `fieldName` | public | `string` | | Set a default name for this field, so that validation feedback will be always&#xA;accessible and linguistically correct | LionField |
23
- | `formatStrategy` | public | `PhoneNumberFormat` | `'international'` | Determines what the formatter output should look like.&#xA;Formatting strategies as provided by google-libphonenumber&#xA;See: https\://www\.npmjs.com/package/google-libphonenumber | LionInputTel |
24
- | `formatCountryCodeStyle` | public | `string` | `'default'` | Extra styling of the format strategy&#xA;default \| parentheses | LionInputTel |
25
- | `allowedRegions` | public | `RegionCode[]` | `[]` | The regions that should be considered when international phone numbers are detected.&#xA;(when not configured, all regions worldwide will be considered) | LionInputTel |
26
- | `_phoneUtil` | protected | `AwesomePhoneNumber\|null` | | | LionInputTel |
27
- | `_inputNode` | protected | `HTMLInputElement \| HTMLTextAreaElement` | | The interactive (form) element. Can be a native element like input/textarea/select or&#xA;an element with tabindex > -1 | LionField |
28
- | `selectionStart` | public | `number` | | | NativeTextFieldMixin |
29
- | `selectionEnd` | public | `number` | | | NativeTextFieldMixin |
30
- | `value` | public | | | The view value. Will be delegated to \`.\_inputNode.value\`&#xA;&#xA;Note: Overrides the implementation from FormatMixin | LionField |
31
- | `_focusableNode` | protected | `HTMLElement` | | The focusable element:&#xA;could be an input, textarea, select, button or any other element with tabindex > -1 | LionField |
32
- | `autocomplete` | public | `string \| undefined` | `undefined` | Delegates this property to input/textarea/select. | NativeTextFieldMixin |
33
- | `formatOn` | protected | `string` | `'change'` | Event that will trigger formatting (more precise, visual update of the view, so the&#xA;user sees the formatted value)&#xA;Default: 'change' | LionField |
34
- | `formatOptions` | public | | `({})` | Configuration object that will be available inside the formatter function | LionField |
35
- | `formattedValue` | public | `string\|undefined` | `undefined` | The view value is the result of the formatter function (when available).&#xA;The result will be stored in the native \_inputNode (usually an input\[type=text]).&#xA;&#xA;Examples:&#xA;- For a date input, this would be '20/01/1999' (dependent on locale).&#xA;- For a number input, this could be '1,234.56' (a String representation of modelValue&#xA;1234.56) | LionField |
36
- | `serializedValue` | public | `string\|undefined` | `undefined` | The serialized version of the model value.&#xA;This value exists for maximal compatibility with the platform API.&#xA;The serialized value can be an interface in context where data binding is not&#xA;supported and a serialized string needs to be set.&#xA;&#xA;Examples:&#xA;- For a date input, this would be the iso format of a date, e.g. '1999-01-20'.&#xA;- For a number input this would be the String representation of a float ('1234.56'&#xA; instead of 1234.56)&#xA;&#xA;When no parser is available, the value is usually the same as the formattedValue&#xA;(being \_inputNode.value) | LionField |
37
- | `_isPasting` | protected | `boolean` | `false` | Whether the user is pasting content. Allows Subclassers to do this in their subclass: | LionField |
38
- | `_isHandlingUserInput` | protected | `boolean` | `false` | Flag that will be set when user interaction takes place (for instance after an 'input'&#xA;event). Will be added as meta info to the \`model-value-changed\` event. Depending on&#xA;whether a user is interacting, formatting logic will be handled differently. | LionField |
39
- | `focused` | public | `boolean` | `false` | Whether the focusable element within (\`.\_focusableNode\`) is focused.&#xA;Reflects to attribute '\[focused]' as a styling hook | LionField |
40
- | `focusedVisible` | public | `boolean` | `false` | Whether the focusable element within (\`.\_focusableNode\`) matches ':focus-visible'&#xA;Reflects to attribute '\[focused-visible]' as a styling hook&#xA;See: https\://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible | LionField |
41
- | `autofocus` | public | `boolean` | `false` | | LionField |
42
- | `label` | public | `string` | `''` | The label text for the input node.&#xA;When no value is defined, textContent of \[slot=label] will be used | LionField |
43
- | `helpText` | public | `string` | `''` | The helpt text for the input node.&#xA;When no value is defined, textContent of \[slot=help-text] will be used | LionField |
44
- | `_labelNode` | protected | | | Element where label will be rendered to | LionField |
45
- | `_helpTextNode` | protected | | | Element where help text will be rendered to | LionField |
46
- | `_feedbackNode` | protected | | | Element where validation feedback will be rendered to | LionField |
47
- | `readOnly` | public | `boolean` | `false` | A Boolean attribute which, if present, indicates that the user should not be able to edit&#xA;the value of the input. The difference between disabled and readonly is that read-only&#xA;controls can still function, whereas disabled controls generally do not function as&#xA;controls until they are enabled.&#xA;(From: https\://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly) | LionField |
48
- | `labelSrOnly` | public | `boolean` | `false` | The label will only be visible for srceen readers when true | LionField |
49
- | `_inputId` | protected | `string` | | Unique id that can be used in all light dom | LionField |
50
- | `_ariaLabelledNodes` | public | `HTMLElement[]` | `[]` | Contains all elements that should end up in aria-labelledby of \`.\_inputNode\` | LionField |
51
- | `_ariaDescribedNodes` | public | `HTMLElement[]` | `[]` | Contains all elements that should end up in aria-describedby of \`.\_inputNode\` | LionField |
52
- | `_repropagationRole` | public | `'child'\|'choice-group'\|'fieldset'` | `'child'` | Based on the role, details of handling model-value-changed repropagation differ. | LionField |
53
- | `_isRepropagationEndpoint` | public | `boolean` | `false` | By default, a field with \_repropagationRole 'choice-group' will act as an&#xA;'endpoint'. This means it will be considered as an individual field: for&#xA;a select, individual options will not be part of the formPath. They&#xA;will.&#xA;Similarly, components that (a11y wise) need to be fieldsets, but 'interaction wise'&#xA;(from Application Developer perspective) need to be more like fields&#xA;(think of an amount-input with a currency select box next to it), can set this&#xA;to true to hide private internals in the formPath. | LionField |
54
- | `modelValue` | public | | | | LionField |
55
- | `type` | public | `string` | `'text'` | | LionInput |
56
- | `placeholder` | public | `string` | `''` | | LionInput |
57
- | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection&#xA;of the parent. Also, it serves as the key of key/value pairs in&#xA; modelValue/serializedValue objects | LionField |
58
- | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or&#xA;ChoiceGroup | LionField |
59
- | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events&#xA;do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.&#xA;Use this option if you know what you're doing. It will then be possible to nest FormControls&#xA;inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
60
- | `_requestedToBeDisabled` | protected | `boolean` | `false` | | LionField |
61
- | `disabled` | public | `boolean` | `false` | | LionField |
62
- | `_feedbackConditionMeta` | protected | | | Allows Subclassers to add meta info for feedbackCondition | LionField |
63
- | `touched` | public | `boolean` | `false` | True when user has focused and left(blurred) the field. | LionField |
64
- | `dirty` | public | `boolean` | `false` | True when user has changed the value of the field. | LionField |
65
- | `prefilled` | public | `boolean` | `false` | True when user has left non-empty field or input is prefilled.&#xA;The name must be seen from the point of view of the input field:&#xA;once the user enters the input field, the value is non-empty. | LionField |
66
- | `filled` | public | `boolean` | `false` | True when the modelValue is non-empty (see \_isEmpty in FormControlMixin) | LionField |
67
- | `_leaveEvent` | protected | `string` | `'blur'` | The event that triggers the touched state | LionField |
68
- | `_valueChangedEvent` | protected | `string` | `'model-value-changed'` | The event that triggers the dirty state | LionField |
69
- | `submitted` | public | | | | LionField |
70
- | `operationMode` | public | `OperationMode` | | Types of input interaction of the FormControl (for instance 'enter'\|'select'\|'upload') | LionField |
71
- | `_allValidators` | protected | `Validator[]` | | Combination of validators provided by Application Developer and the default validators | LionField |
72
- | `hasFeedbackFor` | public | `ValidationType[]` | `[]` | As soon as validation happens (after modelValue/validators/validator param change), this&#xA;array is updated with the active ValidationTypes ('error'\|'warning'\|'success'\|'info' etc.).&#xA;Notice the difference with \`.showsFeedbackFor\`, which filters \`.hasFeedbackFor\` based on&#xA;\`.feedbackCondition()\`.&#xA;&#xA;For styling purposes, will be reflected to \[has-feedback-for="error warning"]. This can&#xA;be useful for subtle visual feedback on keyup, like a red/green border around an input. | LionField |
73
- | `showsFeedbackFor` | public | `ValidationType[]` | `[]` | Based on outcome of feedbackCondition, this array decides what ValidationTypes should be&#xA;shown in validationFeedback, based on meta data like interaction states.&#xA;&#xA;For styling purposes, it reflects it \`\[shows-feedback-for="error warning"]\` | LionField |
74
- | `validationStates` | public | `ValidationStates` | `{}` | The outcome of a validation 'round'. Keyed by ValidationType and Validator name | LionField |
75
- | `isPending` | public | `boolean` | `false` | Flag indicating whether async validation is pending.&#xA;Creates attribute \[is-pending] as a styling hook | LionField |
76
- | `validators` | public | `Validator[]` | `[]` | Used by Application Developers to add Validators to a FormControl. | LionField |
77
- | `defaultValidators` | public | `Validator[]` | `[]` | Used by Subclassers to add default Validators to a particular FormControl.&#xA;A date input for instance, always needs the isDate validator. | LionField |
78
- | `_visibleMessagesAmount` | protected | `number` | `1` | The amount of feedback messages that will visible in LionValidationFeedback | LionField |
79
- | `__SyncUpdatableNamespace` | protected | `SyncUpdatableNamespace` | `{}` | Namespace for this mixin that guarantees naming clashes will not occur... | LionField |
7
+ | Name | Privacy | Type | Default | Description | Inherited From |
8
+ | ---------------------------- | --------- | ----------------------------------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
9
+ | `refs` | public | `object` | `{ /** @type {DropdownRef} */ dropdown: /** @type {DropdownRef} */ (createRef()), }` | | |
10
+ | `_templateDataDropdown` | protected | `TemplateDataForDropdownInputTel` | | This method provides a TemplateData object to be fed to pure template functions, a.k.a.&#xA;Pure Templates™. The goal is to totally decouple presentation from logic here, so that&#xA;Subclassers can override all content without having to loose private info contained&#xA;within the template function that was overridden.&#xA;&#xA;Subclassers would need to make sure all the contents of the TemplateData object are implemented&#xA;by making sure they are coupled to the right 'ref' (\[data-ref=dropdown] in this example),&#xA;with the help of lit's spread operator directive.&#xA;To enhance this process, the TemplateData object is completely typed. Ideally, this would be&#xA;enhanced by providing linters that make sure all of their required members are implemented by&#xA;a Subclasser.&#xA;When a Subclasser wants to add more data, this can be done via: | |
11
+ | `slots` | public | | | Adds ".\_feedbackNode" as described below | LionField |
12
+ | `preferredRegions` | public | `string[]` | `[]` | Regions that will be shown on top of the dropdown | |
13
+ | `_allCountriesLabel` | protected | `string` | `''` | Group label for all countries, when preferredCountries are shown | |
14
+ | `_preferredCountriesLabel` | protected | `string` | `''` | Group label for preferred countries, when preferredCountries are shown | |
15
+ | `activeRegion` | public | `string` | | Currently active region based on:&#xA;1\. allowed regions: get the region from configured allowed regions (if one entry)&#xA;2\. user input: try to derive active region from user input&#xA;3\. locale: try to get the region from locale (\`html\[lang]\` attribute) | LionInputTel |
16
+ | `activePhoneNumberType` | public | | | Type of phone number, derived from textbox value. Enum with values:&#xA;-'fixed-line'&#xA;-'fixed-line-or-mobile'&#xA;-'mobile'&#xA;-'pager'&#xA;-'personal-number'&#xA;-'premium-rate'&#xA;-'shared-cost'&#xA;-'toll-free'&#xA;-'uan'&#xA;-'voip'&#xA;-'unknown'&#xA;See https\://www\.npmjs.com/package/awesome-phonenumber | LionInputTel |
17
+ | `_allowedOrAllRegions` | protected | `RegionCode[]` | | Used for rendering the region/country list | LionInputTel |
18
+ | `_phoneUtilLoadComplete` | protected | `Promise<PhoneNumber>` | | | LionInputTel |
19
+ | `fieldName` | public | `string` | | Set a default name for this field, so that validation feedback will be always&#xA;accessible and linguistically correct | LionField |
20
+ | `formatStrategy` | public | `PhoneNumberFormat` | `'international'` | Determines what the formatter output should look like.&#xA;Formatting strategies as provided by google-libphonenumber&#xA;See: https\://www\.npmjs.com/package/google-libphonenumber | LionInputTel |
21
+ | `formatCountryCodeStyle` | public | `string` | `'default'` | Extra styling of the format strategy&#xA;default \| parentheses | LionInputTel |
22
+ | `allowedRegions` | public | `RegionCode[]` | `[]` | The regions that should be considered when international phone numbers are detected.&#xA;(when not configured, all regions worldwide will be considered) | LionInputTel |
23
+ | `_phoneUtil` | protected | `AwesomePhoneNumber\|null` | | | LionInputTel |
24
+ | `_inputNode` | protected | `HTMLInputElement \| HTMLTextAreaElement` | | The interactive (form) element. Can be a native element like input/textarea/select or&#xA;an element with tabindex > -1 | LionField |
25
+ | `selectionStart` | public | `number` | | | NativeTextFieldMixin |
26
+ | `selectionEnd` | public | `number` | | | NativeTextFieldMixin |
27
+ | `value` | public | | | The view value. Will be delegated to \`.\_inputNode.value\`&#xA;&#xA;Note: Overrides the implementation from FormatMixin | LionField |
28
+ | `_focusableNode` | protected | `HTMLElement` | | The focusable element:&#xA;could be an input, textarea, select, button or any other element with tabindex > -1 | LionField |
29
+ | `autocomplete` | public | `string \| undefined` | `undefined` | Delegates this property to input/textarea/select. | NativeTextFieldMixin |
30
+ | `formatOn` | protected | `string` | `'change'` | Event that will trigger formatting (more precise, visual update of the view, so the&#xA;user sees the formatted value)&#xA;Default: 'change' | LionField |
31
+ | `formatOptions` | public | | `({})` | Configuration object that will be available inside the formatter function | LionField |
32
+ | `formattedValue` | public | `string\|undefined` | `undefined` | The view value is the result of the formatter function (when available).&#xA;The result will be stored in the native \_inputNode (usually an input\[type=text]).&#xA;&#xA;Examples:&#xA;- For a date input, this would be '20/01/1999' (dependent on locale).&#xA;- For a number input, this could be '1,234.56' (a String representation of modelValue&#xA;1234.56) | LionField |
33
+ | `serializedValue` | public | `string\|undefined` | `undefined` | The serialized version of the model value.&#xA;This value exists for maximal compatibility with the platform API.&#xA;The serialized value can be an interface in context where data binding is not&#xA;supported and a serialized string needs to be set.&#xA;&#xA;Examples:&#xA;- For a date input, this would be the iso format of a date, e.g. '1999-01-20'.&#xA;- For a number input this would be the String representation of a float ('1234.56'&#xA; instead of 1234.56)&#xA;&#xA;When no parser is available, the value is usually the same as the formattedValue&#xA;(being \_inputNode.value) | LionField |
34
+ | `_isPasting` | protected | `boolean` | `false` | Whether the user is pasting content. Allows Subclassers to do this in their subclass: | LionField |
35
+ | `_isHandlingUserInput` | protected | `boolean` | `false` | Flag that will be set when user interaction takes place (for instance after an 'input'&#xA;event). Will be added as meta info to the \`model-value-changed\` event. Depending on&#xA;whether a user is interacting, formatting logic will be handled differently. | LionField |
36
+ | `focused` | public | `boolean` | `false` | Whether the focusable element within (\`.\_focusableNode\`) is focused.&#xA;Reflects to attribute '\[focused]' as a styling hook | LionField |
37
+ | `focusedVisible` | public | `boolean` | `false` | Whether the focusable element within (\`.\_focusableNode\`) matches ':focus-visible'&#xA;Reflects to attribute '\[focused-visible]' as a styling hook&#xA;See: https\://developer.mozilla.org/en-US/docs/Web/CSS/:focus-visible | LionField |
38
+ | `autofocus` | public | `boolean` | `false` | | LionField |
39
+ | `label` | public | `string` | `''` | The label text for the input node.&#xA;When no value is defined, textContent of \[slot=label] will be used | LionField |
40
+ | `helpText` | public | `string` | `''` | The helpt text for the input node.&#xA;When no value is defined, textContent of \[slot=help-text] will be used | LionField |
41
+ | `_labelNode` | protected | | | Element where label will be rendered to | LionField |
42
+ | `_helpTextNode` | protected | | | Element where help text will be rendered to | LionField |
43
+ | `_feedbackNode` | protected | | | Element where validation feedback will be rendered to | LionField |
44
+ | `readOnly` | public | `boolean` | `false` | A Boolean attribute which, if present, indicates that the user should not be able to edit&#xA;the value of the input. The difference between disabled and readonly is that read-only&#xA;controls can still function, whereas disabled controls generally do not function as&#xA;controls until they are enabled.&#xA;(From: https\://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-readonly) | LionField |
45
+ | `labelSrOnly` | public | `boolean` | `false` | The label will only be visible for srceen readers when true | LionField |
46
+ | `_inputId` | protected | `string` | | Unique id that can be used in all light dom | LionField |
47
+ | `_ariaLabelledNodes` | public | `HTMLElement[]` | `[]` | Contains all elements that should end up in aria-labelledby of \`.\_inputNode\` | LionField |
48
+ | `_ariaDescribedNodes` | public | `HTMLElement[]` | `[]` | Contains all elements that should end up in aria-describedby of \`.\_inputNode\` | LionField |
49
+ | `_repropagationRole` | public | `'child'\|'choice-group'\|'fieldset'` | `'child'` | Based on the role, details of handling model-value-changed repropagation differ. | LionField |
50
+ | `_isRepropagationEndpoint` | public | `boolean` | `false` | By default, a field with \_repropagationRole 'choice-group' will act as an&#xA;'endpoint'. This means it will be considered as an individual field: for&#xA;a select, individual options will not be part of the formPath. They&#xA;will.&#xA;Similarly, components that (a11y wise) need to be fieldsets, but 'interaction wise'&#xA;(from Application Developer perspective) need to be more like fields&#xA;(think of an amount-input with a currency select box next to it), can set this&#xA;to true to hide private internals in the formPath. | LionField |
51
+ | `modelValue` | public | | | | LionField |
52
+ | `type` | public | `string` | `'text'` | | LionInput |
53
+ | `placeholder` | public | `string` | `''` | | LionInput |
54
+ | `name` | public | `string` | `''` | The name the element will be registered with to the .formElements collection&#xA;of the parent. Also, it serves as the key of key/value pairs in&#xA; modelValue/serializedValue objects | LionField |
55
+ | `_parentFormGroup` | protected | `FormRegistrarHost \| undefined` | `undefined` | The registrar this FormControl registers to, Usually a descendant of FormGroup or&#xA;ChoiceGroup | LionField |
56
+ | `allowCrossRootRegistration` | public | `boolean` | `false` | To encourage accessibility best practices, \`form-element-register\` events&#xA;do not pierce through shadow roots. This forces the developer to create form groups and fieldsets that automatically allow the creation of accessible relationships in the same dom tree.&#xA;Use this option if you know what you're doing. It will then be possible to nest FormControls&#xA;inside shadow dom. See https\://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility | LionField |
57
+ | `_requestedToBeDisabled` | protected | `boolean` | `false` | | LionField |
58
+ | `disabled` | public | `boolean` | `false` | | LionField |
59
+ | `_feedbackConditionMeta` | protected | | | Allows Subclassers to add meta info for feedbackCondition | LionField |
60
+ | `touched` | public | `boolean` | `false` | True when user has focused and left(blurred) the field. | LionField |
61
+ | `dirty` | public | `boolean` | `false` | True when user has changed the value of the field. | LionField |
62
+ | `prefilled` | public | `boolean` | `false` | True when user has left non-empty field or input is prefilled.&#xA;The name must be seen from the point of view of the input field:&#xA;once the user enters the input field, the value is non-empty. | LionField |
63
+ | `filled` | public | `boolean` | `false` | True when the modelValue is non-empty (see \_isEmpty in FormControlMixin) | LionField |
64
+ | `_leaveEvent` | protected | `string` | `'blur'` | The event that triggers the touched state | LionField |
65
+ | `_valueChangedEvent` | protected | `string` | `'model-value-changed'` | The event that triggers the dirty state | LionField |
66
+ | `submitted` | public | | | | LionField |
67
+ | `operationMode` | public | `OperationMode` | | Types of input interaction of the FormControl (for instance 'enter'\|'select'\|'upload') | LionField |
68
+ | `_allValidators` | protected | `Validator[]` | | Combination of validators provided by Application Developer and the default validators | LionField |
69
+ | `hasFeedbackFor` | public | `ValidationType[]` | `[]` | As soon as validation happens (after modelValue/validators/validator param change), this&#xA;array is updated with the active ValidationTypes ('error'\|'warning'\|'success'\|'info' etc.).&#xA;Notice the difference with \`.showsFeedbackFor\`, which filters \`.hasFeedbackFor\` based on&#xA;\`.feedbackCondition()\`.&#xA;&#xA;For styling purposes, will be reflected to \[has-feedback-for="error warning"]. This can&#xA;be useful for subtle visual feedback on keyup, like a red/green border around an input. | LionField |
70
+ | `showsFeedbackFor` | public | `ValidationType[]` | `[]` | Based on outcome of feedbackCondition, this array decides what ValidationTypes should be&#xA;shown in validationFeedback, based on meta data like interaction states.&#xA;&#xA;For styling purposes, it reflects it \`\[shows-feedback-for="error warning"]\` | LionField |
71
+ | `validationStates` | public | `ValidationStates` | `{}` | The outcome of a validation 'round'. Keyed by ValidationType and Validator name | LionField |
72
+ | `isPending` | public | `boolean` | `false` | Flag indicating whether async validation is pending.&#xA;Creates attribute \[is-pending] as a styling hook | LionField |
73
+ | `validators` | public | `Validator[]` | `[]` | Used by Application Developers to add Validators to a FormControl. | LionField |
74
+ | `defaultValidators` | public | `Validator[]` | `[]` | Used by Subclassers to add default Validators to a particular FormControl.&#xA;A date input for instance, always needs the isDate validator. | LionField |
75
+ | `_visibleMessagesAmount` | protected | `number` | `1` | The amount of feedback messages that will visible in LionValidationFeedback | LionField |
76
+ | `__SyncUpdatableNamespace` | protected | `SyncUpdatableNamespace` | `{}` | Namespace for this mixin that guarantees naming clashes will not occur... | LionField |
80
77
 
81
78
  ### Methods
82
79
 
package/docs/components/input-tel-dropdown/extensions.md CHANGED
@@ -22,7 +22,7 @@ export const IntlInputTelDropdown = () => {
22
22
  return html`
23
23
  <intl-input-tel-dropdown
24
24
  .preferredRegions="${['NL', 'PH']}"
25
- .modelValue=${'+639608920056'}
25
+ .modelValue="${'+639608920056'}"
26
26
  label="Telephone number"
27
27
  help-text="Advanced dropdown and styling"
28
28
  name="phoneNumber"
package/docs/components/input-tel-dropdown/overview.md CHANGED
@@ -19,7 +19,7 @@ export const main = () => {
19
19
 
20
20
  ## Features
21
21
 
22
- - Extends our [input-tel](https://github.com/ing-bank/lion/blob/e6f2e59134860fafcd9716ada9dcba6f33b76aa0/docs/components/input-tel/overview.md)
22
+ - Extends our [input-tel](https://github.com/ing-bank/lion/blob/b25478e4cc0cb51c4fda1eccadf5e630b679f53c/docs/components/input-tel/overview.md)
23
23
  - Shows dropdown list with all possible regions
24
24
  - Shows only allowed regions in dropdown list when .allowedRegions is configured
25
25
  - Highlights regions on top of dropdown list when .preferredRegions is configured
package/docs/components/input-tel-dropdown/use-cases.md CHANGED
@@ -46,9 +46,9 @@ export const allowedRegions = () => {
46
46
  <lion-input-tel-dropdown
47
47
  label="Select region via dropdown"
48
48
  help-text="With region code 'NL'"
49
- .modelValue=${'+31612345678'}
49
+ .modelValue="${'+31612345678'}"
50
50
  name="phoneNumber"
51
- .allowedRegions=${['NL', 'DE', 'GB']}
51
+ .allowedRegions="${['NL', 'DE', 'GB']}"
52
52
  ></lion-input-tel-dropdown>
53
53
  <h-output
54
54
  .show="${['modelValue', 'activeRegion']}"
@@ -69,10 +69,10 @@ export const preferredRegionCodes = () => {
69
69
  <lion-input-tel-dropdown
70
70
  label="Select region via dropdown"
71
71
  help-text="Preferred regions show on top"
72
- .modelValue=${'+31612345678'}
72
+ .modelValue="${'+31612345678'}"
73
73
  name="phoneNumber"
74
- .allowedRegions=${['BE', 'CA', 'DE', 'GB', 'NL', 'US']}
75
- .preferredRegions=${['DE', 'NL']}
74
+ .allowedRegions="${['BE', 'CA', 'DE', 'GB', 'NL', 'US']}"
75
+ .preferredRegions="${['DE', 'NL']}"
76
76
  ></lion-input-tel-dropdown>
77
77
  <h-output
78
78
  .show="${['modelValue', 'activeRegion']}"