@lion/ui 0.1.5 → 0.2.1

package/docs/components/select-rich/use-cases.md

@@ -18,23 +18,21 @@ You can set the full `modelValue` for each option, which includes the checked pr
 
 The main feature of this rich select that makes it rich, is that your options can contain HTML.
 
-```js preview-story
-export const optionsWithHTML = () => html`
-  <lion-select-rich label="Favorite color" name="color">
-    <lion-option .choiceValue="${'red'}">
-      <p style="color: red;">I am red</p>
-      <p>and multi Line</p>
-    </lion-option>
-    <lion-option .choiceValue="${'hotpink'}" checked>
-      <p style="color: hotpink;">I am hotpink</p>
-      <p>and multi Line</p>
-    </lion-option>
-    <lion-option .choiceValue="${'teal'}">
-      <p style="color: teal;">I am teal</p>
-      <p>and multi Line</p>
-    </lion-option>
-  </lion-select-rich>
-`;
+```html preview-story
+<lion-select-rich label="Favorite color" name="color">
+  <lion-option .choiceValue="${'red'}">
+    <p style="color: red;">I am red</p>
+    <p>and multi Line</p>
+  </lion-option>
+  <lion-option .choiceValue="${'hotpink'}" checked>
+    <p style="color: hotpink;">I am hotpink</p>
+    <p>and multi Line</p>
+  </lion-option>
+  <lion-option .choiceValue="${'teal'}">
+    <p style="color: teal;">I am teal</p>
+    <p>and multi Line</p>
+  </lion-option>
+</lion-select-rich>
 ```
 
 ## Many Options with Scrolling
@@ -84,14 +82,12 @@ This will block the user from opening the select.
 
 The readonly attribute is delegated to the invoker for disabling opening the overlay, and for styling purposes.
 
-```js preview-story
-export const readOnlyPrefilled = () => html`
-  <lion-select-rich label="Read-only select" readonly name="color">
-    <lion-option .choiceValue=${'red'}>Red</lion-option>
-    <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
-    <lion-option .choiceValue=${'teal'}>Teal</lion-option>
-  </lion-select-rich>
-`;
+```html preview-story
+<lion-select-rich label="Read-only select" readonly name="color">
+  <lion-option .choiceValue=${'red'}>Red</lion-option>
+  <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
+  <lion-option .choiceValue=${'teal'}>Teal</lion-option>
+</lion-select-rich>
 ```
 
 ## Disabled Select
@@ -100,26 +96,22 @@ You can set the `disabled` attribute to disable either specific options or the e
 
 If you disable the entire select, the disabled attribute is also delegated to the invoker, similar to readonly.
 
-```js preview-story
-export const disabledSelect = () => html`
-  <lion-select-rich label="Disabled select" disabled name="color">
-    <lion-option .choiceValue=${'red'}>Red</lion-option>
-    <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
-    <lion-option .choiceValue=${'teal'}>Teal</lion-option>
-  </lion-select-rich>
-`;
+```html preview-story
+<lion-select-rich label="Disabled select" disabled name="color">
+  <lion-option .choiceValue=${'red'}>Red</lion-option>
+  <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
+  <lion-option .choiceValue=${'teal'}>Teal</lion-option>
+</lion-select-rich>
 ```
 
-```js preview-story
-export const disabledOption = () => html`
-  <lion-select-rich label="Disabled options" name="color">
-    <lion-option .choiceValue=${'red'} disabled>Red</lion-option>
-    <lion-option .choiceValue=${'blue'}>Blue</lion-option>
-    <lion-option .choiceValue=${'hotpink'} disabled>Hotpink</lion-option>
-    <lion-option .choiceValue=${'green'}>Green</lion-option>
-    <lion-option .choiceValue=${'teal'} disabled>Teal</lion-option>
-  </lion-select-rich>
-`;
+```html preview-story
+<lion-select-rich label="Disabled options" name="color">
+  <lion-option .choiceValue=${'red'} disabled>Red</lion-option>
+  <lion-option .choiceValue=${'blue'}>Blue</lion-option>
+  <lion-option .choiceValue=${'hotpink'} disabled>Hotpink</lion-option>
+  <lion-option .choiceValue=${'green'}>Green</lion-option>
+  <lion-option .choiceValue=${'teal'} disabled>Teal</lion-option>
+</lion-select-rich>
 ```
 
 ## Render options
@@ -141,10 +133,9 @@ export const renderOptions = ({ shadowRoot }) => {
       2,
     );
   }
-  const mv = { value: obj, checked: false };
   return html`
     <lion-select-rich label="Credit Card" name="color" @model-value-changed=${showOutput}>
-      ${objs.map(obj => html` <lion-option .modelValue=${mv}>${obj.label}</lion-option> `)}
+      ${objs.map(obj => html` <lion-option .choiceValue=${obj}>${obj.label}</lion-option> `)}
     </lion-select-rich>
     <p>Full value:</p>
     <pre id="demoRenderOutput"></pre>
@@ -159,19 +150,17 @@ By default, it will choose based on the user Operating System, but it can be for
 
 This changes the keyboard interaction.
 
-```js preview-story
-export const interactionMode = () => html`
-  <lion-select-rich label="Mac mode" name="color" interaction-mode="mac">
-    <lion-option .choiceValue=${'red'}>Red</lion-option>
-    <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
-    <lion-option .choiceValue=${'teal'}>Teal</lion-option>
-  </lion-select-rich>
-  <lion-select-rich label="Windows/Linux mode" name="color" interaction-mode="windows/linux">
-    <lion-option .choiceValue=${'red'}>Red</lion-option>
-    <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
-    <lion-option .choiceValue=${'teal'}>Teal</lion-option>
-  </lion-select-rich>
-`;
+```html preview-story
+<lion-select-rich label="Mac mode" name="color" interaction-mode="mac">
+  <lion-option .choiceValue=${'red'}>Red</lion-option>
+  <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
+  <lion-option .choiceValue=${'teal'}>Teal</lion-option>
+</lion-select-rich>
+<lion-select-rich label="Windows/Linux mode" name="color" interaction-mode="windows/linux">
+  <lion-option .choiceValue=${'red'}>Red</lion-option>
+  <lion-option .choiceValue=${'hotpink'} checked>Hotpink</lion-option>
+  <lion-option .choiceValue=${'teal'}>Teal</lion-option>
+</lion-select-rich>
 ```
 
 ## Checked index & value
@@ -195,7 +184,7 @@ export const checkedIndexAndValue = ({ shadowRoot }) => html`
       type="number"
       @change=${e => {
         const selectEl = shadowRoot.querySelector('#checkedRichSelect');
-        selectEl.checkedIndex = e.target.value;
+        selectEl.checkedIndex = Number(e.target.value);
       }}
     />
   </div>
@@ -232,14 +221,12 @@ However, this allows the user to explicitly select this option.
 Often, you may want a placeholder that appears initially, but cannot be selected explicitly by the user.
 For this you can use `has-no-default-selected` attribute.
 
-```js preview-story
-export const noDefaultSelection = () => html`
+```html preview-story
   <lion-select-rich name="favoriteColor" label="Favorite color" has-no-default-selected>
     <lion-option .choiceValue=${'red'}>Red</lion-option>
     <lion-option .choiceValue=${'hotpink'}>Hotpink</lion-option>
     <lion-option .choiceValue=${'teal'}>Teal</lion-option>
   </lion-select-rich>
-`;
 ```
 
 > By default, the placeholder is completely empty in the `LionSelectInvoker`,
@@ -249,12 +236,10 @@ export const noDefaultSelection = () => html`
 
 If there is a single option rendered, then `singleOption` property is set to `true` on `lion-select-rich` and invoker as well. Invoker also gets `single-option` which can be used to having desired templating and styling. As in here the arrow is not displayed for single option
 
-```js preview-story
-export const singleOption = () => html`
-  <lion-select-rich label="Single Option" name="color">
-    <lion-option .choiceValue=${'red'}>Red</lion-option>
-  </lion-select-rich>
-`;
+```html preview-story
+<lion-select-rich label="Single Option" name="color">
+  <lion-option .choiceValue=${'red'}>Red</lion-option>
+</lion-select-rich>
 ```
 
 When adding/removing options the `singleOption` will only be `true` when there is exactly one option.
@@ -317,7 +302,7 @@ LionSelectRich will give it acces to:
 - LionSelectRich itself, via `.hostElement`
 
 Code of an advanced custom invoker is shown below (this is the code for the
-invoker used in [IntlSelectRich](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/select-rich/examples.md)).
+invoker used in [IntlSelectRich](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/select-rich/examples.md)).
 The invoker is usually added in the invoker slot of the LionSelectRich subclass.
 However, it would also be possible for an application developer to provide the invoker
 by putting it in light dom:

package/docs/components/tabs/examples.md

@@ -9,7 +9,7 @@ import './src/lea-tab-panel.js';
 
 ## Lea Tabs
 
-Learn how to create the `lea tabs` in our ["introducing lion" blogpost](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/blog/ing-open-sources-lion.md).
+Learn how to create the `lea tabs` in our ["introducing lion" blogpost](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/blog/ing-open-sources-lion.md).
 
 ```js preview-story
 export const main = () => html`

package/docs/fundamentals/index.md

@@ -9,11 +9,11 @@ Here you find more details about what we offer.
 
 Let's see what each section describes.
 
-1. [](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/core/overview.md) <br>
+1. [Systems](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/core/overview.md) <br>
    These are the fundamental systems that power all of our components.
-2. [Tools](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/tools/helpers/overview.md) <br>
+2. [Tools](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/tools/helpers/overview.md) <br>
    Frontend Tools useful for web development but are not visual and therefore are not components.
-3. [Node Tools](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/babel-plugin-extend-docs/overview.md) <br>
+3. [Node Tools](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/babel-plugin-extend-docs/overview.md) <br>
    Node tools to analyse the code and for extending the documentation.
-4. [Rationales](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/rationales/side-effects.md) <br>
+4. [Rationales](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/rationales/side-effects.md) <br>
    The reasoning behind some of our decisions.

package/docs/fundamentals/node-tools/providence-analytics/LocalConfiguration.md

@@ -45,7 +45,7 @@ export default {
 ### referenceCollections
 
 A list of file system paths. They can be defined relative from the current project root or they can be full paths.
-When a [MatchAnalyzer](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/providence-analytics/analyzer.md) like `match-imports` or `match-subclasses` is used, the default reference(s) can be configured here. For instance: ['/path/to/@lion/ui/form.js']
+When a [MatchAnalyzer](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/providence-analytics/analyzer.md) like `match-imports` or `match-subclasses` is used, the default reference(s) can be configured here. For instance: ['/path/to/@lion/ui/form.js']
 
 An example:
 

package/docs/fundamentals/node-tools/providence-analytics/QueryResult.md

@@ -108,4 +108,4 @@ QueryOutput structure could be simplified in the future.
 
 The output files stored in the file system always need to be machine independent:
 this means that all machine specific information, like a complete filepath, needs to be removed from a QueryOutput (paths relative from project root are still allowed).
-In that way, the caching mechanism (based on hash comparisons) as described in [Analyzer](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/providence-analytics/analyzer.md) is guaranteed to work across different machines.
+In that way, the caching mechanism (based on hash comparisons) as described in [Analyzer](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/providence-analytics/analyzer.md) is guaranteed to work across different machines.

package/docs/fundamentals/node-tools/providence-analytics/analyzer.md

@@ -7,7 +7,7 @@ A few examples are:
 - find-exports
 - match-imports
 
-An analyzer will give back a [QueryResult](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) that will be written to the file system by Providence.
+An analyzer will give back a [QueryResult](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) that will be written to the file system by Providence.
 All analyzers need to extend from the `Analyzer` base class, found in `src/program/analyzers/helpers`.
 
 ## Public api

package/docs/fundamentals/node-tools/providence-analytics/dashboard.md

@@ -1,6 +1,6 @@
 # Node Tools >> Providence Analytics >> Dashboard ||30
 
-An interactive overview of all aggregated [QueryResults](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) can be found in the dashboard.
+An interactive overview of all aggregated [QueryResults](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/providence-analytics/QueryResult.md) can be found in the dashboard.
 The dashboard is a small nodejs server (based on es-dev-server + middleware) and a frontend
 application.
 

package/docs/fundamentals/node-tools/providence-analytics/overview.md

@@ -47,7 +47,7 @@ npm i --save-dev providence-analytics
 You are now ready to use providence in your project. All
 data will be stored in json files in the folder `./providence-output`
 
-![CLI](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/providence-analytics/assets/provicli.gif 'CLI')
+![CLI](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/providence-analytics/assets/provicli.gif 'CLI')
 
 ## Setup: Dashboard
 
@@ -76,7 +76,7 @@ export default {
 
 Run `npm run providence:dashboard`
 
-![dashboard](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/providence-analytics/assets/providash.gif 'dashboard')
+![dashboard](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/providence-analytics/assets/providash.gif 'dashboard')
 
 ## Setup: about result output
 
@@ -153,7 +153,7 @@ Now you will get a list of all predefined analyzers:
 - match-subclasses
 - etc...
 
-![Analyzer query](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/providence-analytics/assets/analyzer-query.gif 'Analyzer query')
+![Analyzer query](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/providence-analytics/assets/analyzer-query.gif 'Analyzer query')
 
 <!--
 ## Running providence from its own repo

package/docs/fundamentals/node-tools/publish-docs/overview.md

@@ -31,7 +31,7 @@ For a Mono Repository
    ```md
    # My Pkg
 
-   [=> See Source <=](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/docs/deep/dir/overview.md)
+   [=> See Source <=](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/docs/deep/dir/overview.md)
    ```
 
 ## CLI flags
@@ -61,7 +61,7 @@ Bring the `overview.md` in a docs folder along.
 👉 `packages/[my-package]/docs/overview.md`
 
 ```md
-[=> See Source <=](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/docs/deep/dir/overview.md)
+[=> See Source <=](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/docs/deep/dir/overview.md)
 ```
 
 Add a `use-cases.md`
@@ -69,7 +69,7 @@ Add a `use-cases.md`
 👉 `packages/[my-package]/docs/use-cases.md`
 
 ```md
-[=> See Source <=](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/docs/deep/dir/use-cases.md)
+[=> See Source <=](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/docs/deep/dir/use-cases.md)
 ```
 
 So you will end up with something like this in your package.

package/docs/fundamentals/node-tools/rocket-preset-extend-lion-docs/overview.md

@@ -7,7 +7,7 @@ To do this automatically you can use this preset for [rocket](https://rocket.mod
 
 ## Features
 
-- Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/remark-extend/overview.md)
+- Import lion documentation and adjust it using [remark-extend](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/remark-extend/overview.md)
 - Renames named imports and all it's usage
 - Adjusts import paths
 - Replace tags in template literals
@@ -38,7 +38,7 @@ export default {
 
 ## Reusing documentation
 
-To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/node-tools/remark-extend/overview.md).
+To take an existing documentation you can "import" it using [remark-extend](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/node-tools/remark-extend/overview.md).
 
 As an example you can create `docs/components/tabs/overview.md`.
 

package/docs/fundamentals/systems/core/overview.md

@@ -15,7 +15,7 @@ import { LitElement, html, render } from 'lit-element';
 
 ## Features
 
-- [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/core/#deduping-of-mixins)
+- [function to deduplicate mixins (dedupeMixin)](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/core/#deduping-of-mixins)
 - Mixin to handle disabled (DisabledMixin)
 - Mixin to handle disabled AND tabIndex (DisabledWithTabIndexMixin)
 - Mixin to manage auto-generated needed slot elements in light dom (SlotMixin)

package/docs/fundamentals/systems/form/formatting-and-parsing.md

@@ -23,7 +23,7 @@ Our fields can automatically format/parse/serialize user input or an input set i
 
 Below are some concrete examples of implementations of formatters and parsers mimicking a (basic) amount input.
 
-> For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-amount/overview.md).
+> For an actual amount input, check out [lion-input-amount](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-amount/overview.md).
 > This comes with its own formatter, parser, serializer.
 
 ### Parsers & modelValue
@@ -230,16 +230,16 @@ Below we show three flow diagrams to show the flow of formatting, serializing an
 
 Where a user changes the input with their keyboard:
 
-![Standard flow](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
+![Standard flow](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/assets/FormatMixinDiagram-1.svg 'Standard flow')
 
 ### Unparseable flow
 
 Where a user sets the input to something that is not parseable by the parser:
 
-![Unparseable flow](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
+![Unparseable flow](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/assets/FormatMixinDiagram-2.svg 'Unparseable flow')
 
 ### Imperative / programmatic flow
 
 Where the developer sets the modelValue of the input programmatically:
 
-![Imperative flow](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')
+![Imperative flow](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/assets/FormatMixinDiagram-3.svg 'Imperative flow')

package/docs/fundamentals/systems/form/model-value.md

@@ -21,7 +21,7 @@ level, via:
 > Internal/private concepts like viewValue, formattedValue, serializedValue are therefore not
 > recommended as a means of interaction.
 
-For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/formatting-and-parsing.md)
+For more information about parsing and the Unparseable type, see [Formatting and Parsing](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/formatting-and-parsing.md)
 
 ### Event meta
 

package/docs/fundamentals/systems/form/overview.md

@@ -20,9 +20,9 @@ Fields (think of an input, textarea, select) are the actual form controls the en
 
 On top of this, they feature:
 
-- [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
-- Advanced [validation](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/validate.md) possibilities.
-- Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/interaction-states.md).
+- [formatting/parsing/serializing](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/formatting-and-parsing.md) of view values.
+- Advanced [validation](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/validate.md) possibilities.
+- Creation of advanced user interaction scenarios via [interaction states](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/interaction-states.md).
 - Provision of labels and help texts in an easy, declarative manner.
 - Accessibility out of the box.
 - Advanced styling possibilities: map your own Design System to the internal HTML structure.
@@ -31,33 +31,33 @@ On top of this, they feature:
 
 ### Platform fields (wrappers)
 
-- [LionInput](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input/overview.md), a wrapper for `<input>`.
-- [LionTextarea](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
-- [LionSelect](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/select/overview.md), a wrapper for `<select>`.
+- [LionInput](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input/overview.md), a wrapper for `<input>`.
+- [LionTextarea](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/textarea/overview.md), a wrapper for `<textarea>`.
+- [LionSelect](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/select/overview.md), a wrapper for `<select>`.
 
 ### Custom fields (wrappers)
 
-Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
+Whenever a native form control doesn't exist or is not sufficient, a [custom form field](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/guides/how-to/create-a-custom-field.md) should be created. One could think of components like:
 
-- [LionCombobox](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/combobox/overview.md), a custom implementation of a combobox.
-- [LionDate](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
-- [LionDatepicker](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
-- [LionListbox](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/listbox/overview.md), a custom implementation of a listbox.
-- [LionInputAmount](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
-- [LionInputEmail](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
-- [LionInputIban](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
-- [LionInputRange](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
-- [LionInputStepper](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
-- [LionSelectRich](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
+- [LionCombobox](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/combobox/overview.md), a custom implementation of a combobox.
+- [LionDate](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-date/overview.md), an alternative for `<input type="date">`.
+- [LionDatepicker](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-datepicker/overview.md), an alternative for `<input type="date">` including a calendar dropdown.
+- [LionListbox](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/listbox/overview.md), a custom implementation of a listbox.
+- [LionInputAmount](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-amount/overview.md), an alternative for `<input type="number">` special for amounts.
+- [LionInputEmail](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-email/overview.md), an alternative for `<input type="email">`.
+- [LionInputIban](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-iban/overview.md), an ING specific for an input with IBAN numbers.
+- [LionInputRange](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-range/overview.md), an alternative for `<input type="range">`.
+- [LionInputStepper](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/input-stepper/overview.md), an alternative for `<input type="number">`.
+- [LionSelectRich](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/select-rich/overview.md), an alternative for `<select>` with multiline options.
 
 ### Choice Input Fields
 
 For form controls which return a `checked-state` you can use the `lion-choice-input` mixin. It is used in:
 
-- [LionCheckbox](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
+- [LionCheckbox](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/checkbox-group/overview.md), a wrapper for `<input type="checkbox">`.
 - LionOption, an alternative for `<option>`.
-- [LionRadio](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
-- [LionSwitch](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/switch/overview.md), a custom implementation of a switch.
+- [LionRadio](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/radio-group/overview.md), a wrapper for `<input type="radio">`.
+- [LionSwitch](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/switch/overview.md), a custom implementation of a switch.
 
 Which contains the following features:
 
@@ -69,14 +69,14 @@ Which contains the following features:
 
 Fieldsets are groups of fields. They can be considered fields on their own as well, since they partly share the normalized API via `FormControlMixin`. Fieldsets are the basis for:
 
-- [LionFieldset](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
-- [LionForm](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
-- [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
-- [LionRadioGroup](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
+- [LionFieldset](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/fieldset/overview.md), a wrapper around multiple input fields or other fieldsets.
+- [LionForm](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/form/overview.md), enhances the functionality of the native `<form>` component.
+- [LionCheckboxGroup](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/checkbox-group/overview.md), a wrapper component for multiple checkboxes.
+- [LionRadioGroup](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/radio-group/overview.md), a wrapper component for multiple radio inputs.
 
 ## Other Resources
 
-- [Model Value](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/model-value.md)
-- [Formatting and parsing](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/formatting-and-parsing.md)
-- [Interaction states](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/interaction-states.md)
-- [Validation System](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/validate.md)
+- [Model Value](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/model-value.md)
+- [Formatting and parsing](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/formatting-and-parsing.md)
+- [Interaction states](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/interaction-states.md)
+- [Validation System](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/validate.md)

package/docs/fundamentals/systems/form/validate.md

@@ -58,7 +58,7 @@ Validation happens on every change of `modelValue`. A change in modelValue can b
 
 ## When validation feedback will be shown
 
-Although validation happens realtime under the hood, displaying validity feedback in realtime may not always lead to the desired User Experience. Together with [interaction states](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/form/interaction-states.md),
+Although validation happens realtime under the hood, displaying validity feedback in realtime may not always lead to the desired User Experience. Together with [interaction states](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/form/interaction-states.md),
 validity states can determine whether a validation message should be shown along the input field.
 
 ## Assessing field validation state programmatically

package/docs/fundamentals/systems/localize/overview.md

@@ -9,15 +9,15 @@ In it's simplest form it is a function that returns the translated text for a na
 - Formatting of numbers, amounts
 - Formatting of dates
 
-Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/localize/use-cases.md).
+Further examples and a more in depth description can be found at the [Use Cases Page](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/localize/use-cases.md).
 
 ## Content
 
 | Feature                                  | Description                                   |
 | ---------------------------------------- | --------------------------------------------- |
-| [Translate Text](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/localize/text.md)    | Load and translate text in multiple languages |
-| [Format Numbers](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages          |
-| [Format Dates](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/localize/dates.md)     | Format dates in multiple languages            |
+| [Translate Text](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/localize/text.md)    | Load and translate text in multiple languages |
+| [Format Numbers](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/localize/numbers.md) | Format numbers in multiple languages          |
+| [Format Dates](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/localize/dates.md)     | Format dates in multiple languages            |
 
 ## Installation
 

package/docs/fundamentals/systems/overlays/configuration.md

@@ -68,7 +68,7 @@ export const placementGlobal = () => {
 
 ## isTooltip (placementMode: 'local')
 
-As specified in the [overlay rationale](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/overlays/rationale.md) there are only two official types of overlays: dialogs and tooltips. And their main differences are:
+As specified in the [overlay rationale](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/overlays/rationale.md) there are only two official types of overlays: dialogs and tooltips. And their main differences are:
 
 - Dialogs have a modal option, tooltips don’t
 - Dialogs have interactive content, tooltips don’t
@@ -373,7 +373,7 @@ Features:
 
 > Popper strictly is scoped on positioning. **It does not change the dimensions of the content node nor the invoker node**.
 > This also means that if you use the arrow feature, you are in charge of styling it properly, use the data-popper-placement attribute for this.
-> An example implementation can be found in [lion-tooltip](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/tooltip/overview.md), where an arrow is set by default.
+> An example implementation can be found in [lion-tooltip](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/tooltip/overview.md), where an arrow is set by default.
 
 To override the default options we set for local mode, you add a `popperConfig` object to the config passed to the OverlayController.
 Here's a succinct overview of some often used popper properties:

package/docs/fundamentals/systems/overlays/overview.md

@@ -6,7 +6,7 @@ Manages their position on the screen relative to other elements, including other
 
 Its purpose is to make it easy to use our Overlay System declaratively. It can be easily extended where needed, to override event listeners and more.
 
-See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/components/tooltip/overview.md) for example Web Component implementations using the Overlay System.
+See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/components/tooltip/overview.md) for example Web Component implementations using the Overlay System.
 
 ## Features
 
@@ -18,9 +18,9 @@ See [lion-dialog](../../../components/dialog/overview.md) and [lion-tooltip](htt
 - lion-overlay web component:
   - Show content when clicking the invoker
   - Have a `.config` object to set or update the OverlayController's configuration
-- [**OverlaysManager**](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/overlays/use-cases.md#overlaysmanager), a global repository keeping track of all different types of overlays
-- [**OverlayController**](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
-- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/overlays/use-cases.md#overlaymixin), a mixin that can be used to create webcomponents that use the OverlayController under the hood
+- [**OverlaysManager**](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/overlays/use-cases.md#overlaysmanager), a global repository keeping track of all different types of overlays
+- [**OverlayController**](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/overlays/use-cases.md#overlaycontroller), a single controller class for handling overlays
+- [**OverlayMixin**](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/overlays/use-cases.md#overlaymixin), a mixin that can be used to create webcomponents that use the OverlayController under the hood
 
 Usually you will use `lion-dialog` (or `lion-tooltip` if this makes more sense).
 
@@ -110,9 +110,4 @@ class MyOverlayComponent extends OverlayMixin(LitElement) {
 
 ## Rationales
 
-Please check the [system rationals](https://github.com/ing-bank/lion/blob/ecea06cb6eba324d87a001a6ecb95ce7172b2111/docs/fundamentals/systems/overlays/rationale.md) folder, where we go more in-depth.
-
-### Aria roles
-
-- No `aria-controls` as support for it is not quite there yet
-- No `aria-haspopup`. People knowing the haspopup and hear about it don’t expect a dialog to open (at this moment in time) but expect a sub-menu. Until support for the dialog value has better implementation, it’s probably best to not use aria-haspopup on the element that opens the modal dialog.
+Please check the [system rationals](https://github.com/ing-bank/lion/blob/7b2a234c6c05397bc2e2e944c5efbdea08d09d2b/docs/fundamentals/systems/overlays/rationale.md) folder, where we go more in-depth.

package/docs/fundamentals/systems/overlays/rationale.md

@@ -222,11 +222,8 @@ global(modal) dialog.
 
 ## Considerations
 
-### Future for mode local (Popper)
+We use the native dialog purely because it renders to the "top layer". Not because of its accessible role, which varies per component. In the future we can use the popover attribute(<https://open-ui.org/components/popover.research.explainer/>) for this (which neatly differentiates between presentation and semantics).
 
-- Default overflow and/or max-width behavior when content is too wide or high for the viewport.
+So in our use of the dialog we want also a dialog that only does presentation (rendering on top layer in this case), but we want to check the semantics ourselves. Hence: `role="none"`. Even though the outcome is completely accessible, AXE-core uses this rule as a kind of "precautionary measure".
 
-### Aria roles
-
-- No `aria-controls` as support for it is not quite there yet
-- No `aria-haspopup`. People knowing the haspop up and hear about it don’t expect a dialog to open (at this moment in time) but expect a sub-menu. Until support for the dialog value has better implementation, it’s probably best to not use aria-haspopup on the element that opens the modal dialog.
+After a cost/benefit analysis, we choose to be temporarily incompatible with AXE-core. Therefore, we recommend running tests with `{ ignoredRules: ['aria-allowed-role'] }`. When the popover is stable and used underwater in lion overlays, AXE can again be run without this ignoredRule.