@lion/ui 0.8.0 → 0.8.2

package/custom-elements.json

@@ -2100,6 +2100,36 @@
         }
       ]
     },
+    {
+      "kind": "javascript-module",
+      "path": "exports/define-helpers/sb-action-logger.js",
+      "declarations": [],
+      "exports": [
+        {
+          "kind": "custom-element-definition",
+          "name": "sb-action-logger",
+          "declaration": {
+            "name": "SbActionLogger",
+            "module": "/exports/helpers.js"
+          }
+        }
+      ]
+    },
+    {
+      "kind": "javascript-module",
+      "path": "exports/define-helpers/sb-locale-switcher.js",
+      "declarations": [],
+      "exports": [
+        {
+          "kind": "custom-element-definition",
+          "name": "sb-locale-switcher",
+          "declaration": {
+            "name": "SbLocaleSwitcher",
+            "module": "/exports/helpers.js"
+          }
+        }
+      ]
+    },
     {
       "kind": "javascript-module",
       "path": "exports/define/lion-accordion.js",
@@ -2790,36 +2820,6 @@
         }
       ]
     },
-    {
-      "kind": "javascript-module",
-      "path": "exports/define-helpers/sb-action-logger.js",
-      "declarations": [],
-      "exports": [
-        {
-          "kind": "custom-element-definition",
-          "name": "sb-action-logger",
-          "declaration": {
-            "name": "SbActionLogger",
-            "module": "/exports/helpers.js"
-          }
-        }
-      ]
-    },
-    {
-      "kind": "javascript-module",
-      "path": "exports/define-helpers/sb-locale-switcher.js",
-      "declarations": [],
-      "exports": [
-        {
-          "kind": "custom-element-definition",
-          "name": "sb-locale-switcher",
-          "declaration": {
-            "name": "SbLocaleSwitcher",
-            "module": "/exports/helpers.js"
-          }
-        }
-      ]
-    },
     {
       "kind": "javascript-module",
       "path": "components/accordion/src/LionAccordion.js",
@@ -3246,6 +3246,17 @@
               },
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "DisabledWithTabIndexMixin",
+                "module": "components/core/src/DisabledWithTabIndexMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "__internalSetTabIndex",
@@ -3550,6 +3561,17 @@
               },
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionButton",
+                "module": "components/button/src/LionButton.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "__internalSetTabIndex",
@@ -3974,6 +3996,17 @@
               },
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionButton",
+                "module": "components/button/src/LionButton.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "__internalSetTabIndex",
@@ -4685,6 +4718,13 @@
               "description": "This exposes an interface for datepickers that want to\nreinitialize when calendar is opened",
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "__calculateInitialCentralDate",
@@ -7128,6 +7168,17 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -9710,7 +9761,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -10808,7 +10859,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -11282,7 +11333,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -12959,7 +13010,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -18782,6 +18833,12 @@
                 "module": "components/core/src/DisabledMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve"
+            },
             {
               "kind": "method",
               "name": "__internalSetTabIndex",
@@ -19396,6 +19453,17 @@
                 "module": "components/overlays/src/OverlayMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "OverlayMixin",
+                "module": "components/overlays/src/OverlayMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "field",
               "name": "_overlayInvokerNode",
@@ -20890,6 +20958,17 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -23624,7 +23703,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -25301,7 +25380,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -27913,7 +27992,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -29006,7 +29085,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -29458,7 +29537,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -31135,7 +31214,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -34172,6 +34251,17 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -36471,7 +36561,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -37564,7 +37654,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -37960,7 +38050,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -38036,7 +38126,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -39461,6 +39551,16 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -40356,7 +40456,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -40443,7 +40543,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -40688,7 +40788,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -40828,6 +40928,12 @@
               "privacy": "protected",
               "readonly": true
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -41301,7 +41407,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -41664,7 +41770,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -42002,6 +42108,16 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -42623,7 +42739,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -43049,7 +43165,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -43930,7 +44046,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -45589,7 +45705,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -45783,7 +45899,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration"
             }
@@ -45819,7 +45935,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration"
             }
@@ -46066,7 +46182,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -46111,7 +46227,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -47488,6 +47604,16 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -48383,7 +48509,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -48470,7 +48596,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -48731,7 +48857,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -49594,6 +49720,16 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "SyncUpdatableMixin",
+                "module": "components/form-core/src/utils/SyncUpdatableMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -50215,7 +50351,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -50551,7 +50687,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -50754,7 +50890,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -56129,7 +56265,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -56860,6 +56996,16 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -57663,7 +57809,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -57903,7 +58049,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -59559,6 +59705,16 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -60395,7 +60551,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -60482,7 +60638,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -60649,7 +60805,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -61489,7 +61645,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -61612,6 +61768,16 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "SyncUpdatableMixin",
+                "module": "components/form-core/src/utils/SyncUpdatableMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -63032,7 +63198,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -63151,7 +63317,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -64416,6 +64582,17 @@
                 "module": "components/fieldset/src/LionFieldset.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionFieldset",
+                "module": "components/fieldset/src/LionFieldset.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -66476,6 +66653,13 @@
           "description": "Custom element for rendering SVG icons",
           "name": "LionIcon",
           "members": [
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "privacy": "public"
+            },
             {
               "kind": "field",
               "name": "svg",
@@ -67510,6 +67694,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -68171,7 +68366,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -69280,7 +69475,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -69536,7 +69731,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -70726,6 +70921,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -71372,7 +71578,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -72490,7 +72696,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -72738,7 +72944,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -73435,7 +73641,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -73652,6 +73858,17 @@
                 "module": "components/overlays/src/OverlayMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "field",
               "name": "_overlayReferenceNode",
@@ -75178,7 +75395,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -76493,7 +76710,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -77569,6 +77786,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -78239,7 +78467,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -79357,7 +79585,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -79601,7 +79829,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -80486,7 +80714,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -80635,6 +80863,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -81205,7 +81444,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -83050,7 +83289,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -84752,6 +84991,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -85422,7 +85672,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -86540,7 +86790,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -86796,7 +87046,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -88692,6 +88942,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -89319,7 +89580,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -90437,7 +90698,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -90721,7 +90982,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -91985,6 +92246,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -92655,7 +92927,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -93773,7 +94045,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -94165,7 +94437,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -95462,6 +95734,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -96090,7 +96373,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -97208,7 +97491,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -97524,7 +97807,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -98793,6 +99076,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -99463,7 +99757,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -100581,7 +100875,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -100868,7 +101162,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -102300,6 +102594,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -102915,7 +103220,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -104033,7 +104338,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -104269,7 +104574,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -108512,6 +108817,16 @@
                 "module": "components/form-core/src/InteractionStateMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "InteractionStateMixin",
+                "module": "components/form-core/src/InteractionStateMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -109085,7 +109400,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -109368,7 +109683,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -110789,7 +111104,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -111778,7 +112093,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -111909,7 +112224,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -112052,15 +112367,91 @@
           "name": "LocalizeManager",
           "members": [
             {
-              "kind": "method",
-              "name": "_setupTranslationToolSupport",
-              "privacy": "protected"
+              "kind": "field",
+              "name": "formatNumberOptions",
+              "type": {
+                "text": "object"
+              },
+              "default": "{ returnIfNaN: '', /** @type {Map<string, NumberPostProcessor>} */ postProcessors: new Map(), }",
+              "description": "The localize system uses (normalized) Intl for formatting numbers.\nIt's possible to customize this output per locale",
+              "privacy": "public"
             },
             {
-              "kind": "method",
-              "name": "teardown",
+              "kind": "field",
+              "name": "formatDateOptions",
+              "type": {
+                "text": "object"
+              },
+              "default": "{ /** @type {Map<string, DatePostProcessor>} */ postProcessors: new Map(), }",
+              "description": "The localize system uses (normalized) Intl for formatting dates.\nIt's possible to customize this output per locale",
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "#shouldHandleTranslationTools",
+              "privacy": "private",
+              "type": {
+                "text": "boolean"
+              },
+              "default": "false",
+              "description": "Although it's common to configure the language via the html[lang] attribute,\nthe lang attribute can be changed by 3rd party translation tools like Google Translate.\n\n## Why is this a potential problem?\nThe localize system reads from html[lang] for its original configuration. Let's say it's\nconfigured as \"en-US\" by the developer. This means all translation data are fetched for locale \"en-US\".\n\nNow the Google Translate plugin kicks in. It will automatically translate all English texts found into\nChinese texts. Everything looks fine... But Google Translate also sets html[lang] to \"zh-CN\":\nour localize system responds by trying to fetch Chinese translation data.\nTwo problems can occur here:\n- the Chinese translations don't exist\n- Google Translate expects to translate from English to Chinese... and now we suddenly serve Chinese text\nourselves... not what we intended.\n\n## How can we solve this?\nVia `html[data-localize-lang]`, developers are allowed to set the initial locale, without\nhaving to worry about whether locale is initialized before 3rd parties like Google Translate.\nWhen this value differs from html[lang], we assume the 3rd party took\ncontrol over the page language and we set this.#localeSetByTranslationTool to html[lang]"
+            },
+            {
+              "kind": "field",
+              "name": "#localeProvidedViaDataLangAttr",
+              "privacy": "private",
+              "type": {
+                "text": "string"
+              },
+              "default": "''",
+              "description": "The locale that is configured on html[data-localize-lang]"
+            },
+            {
+              "kind": "field",
+              "name": "#localeSetByTranslationTool",
+              "privacy": "private",
+              "type": {
+                "text": "string|null"
+              },
+              "default": "null",
+              "description": "The locale that is set on html[lang] by a 3rd party translation tool like Googl Translate"
+            },
+            {
+              "kind": "field",
+              "name": "__storage",
+              "type": {
+                "text": "Object<string, Object<string, Object>>"
+              },
+              "default": "{}",
+              "privacy": "private"
+            },
+            {
+              "kind": "field",
+              "name": "__namespacePatternsMap",
+              "default": "new Map()",
+              "type": {
+                "text": "Map<RegExp|string, function>"
+              },
+              "privacy": "private"
+            },
+            {
+              "kind": "field",
+              "name": "__namespaceLoadersCache",
+              "type": {
+                "text": "Object<string, function|null>"
+              },
+              "default": "{}",
+              "privacy": "private"
+            },
+            {
+              "kind": "field",
+              "name": "__namespaceLoaderPromisesCache",
+              "type": {
+                "text": "Object<string, Object<string, Promise<Object|void>>>"
+              },
+              "default": "{}",
+              "privacy": "private"
+            },
             {
               "kind": "field",
               "name": "locale",
@@ -112071,7 +112462,7 @@
               },
               "parameters": [
                 {
-                  "name": "value",
+                  "name": "newLocale",
                   "type": {
                     "text": "string"
                   }
@@ -112079,46 +112470,15 @@
               ],
               "privacy": "public"
             },
-            {
-              "kind": "method",
-              "name": "_setHtmlLangAttribute",
-              "parameters": [
-                {
-                  "name": "locale",
-                  "type": {
-                    "text": "string"
-                  }
-                }
-              ],
-              "privacy": "protected"
-            },
-            {
-              "kind": "method",
-              "name": "__handleLanguageOnly",
-              "parameters": [
-                {
-                  "name": "value",
-                  "type": {
-                    "text": "string"
-                  }
-                }
-              ],
-              "privacy": "private"
-            },
             {
               "kind": "field",
               "name": "loadingComplete",
+              "readonly": true,
               "return": {
                 "type": {
-                  "text": "Promise.<Object|void>"
+                  "text": "Promise<Object|void>"
                 }
               },
-              "readonly": true,
-              "privacy": "public"
-            },
-            {
-              "kind": "method",
-              "name": "reset",
               "privacy": "public"
             },
             {
@@ -112188,7 +112548,7 @@
               ],
               "return": {
                 "type": {
-                  "text": "Promise.<Object>"
+                  "text": "Promise<Object>"
                 }
               },
               "privacy": "public"
@@ -112216,7 +112576,7 @@
               ],
               "return": {
                 "type": {
-                  "text": "Promise.<Object|void>"
+                  "text": "Promise<Object|void>"
                 }
               },
               "privacy": "public"
@@ -112235,7 +112595,7 @@
                   "name": "vars",
                   "optional": true,
                   "type": {
-                    "text": "Object.<string,?>"
+                    "text": "Object<string,?>"
                   }
                 },
                 {
@@ -112254,6 +112614,67 @@
               },
               "privacy": "public"
             },
+            {
+              "kind": "method",
+              "name": "teardown",
+              "privacy": "public"
+            },
+            {
+              "kind": "method",
+              "name": "reset",
+              "privacy": "public"
+            },
+            {
+              "kind": "method",
+              "name": "setDatePostProcessorForLocale",
+              "parameters": [
+                {
+                  "name": "{ locale, postProcessor }"
+                },
+                {
+                  "name": "options",
+                  "type": {
+                    "text": "{locale:string, postProcessor:DatePostProcessor}"
+                  }
+                }
+              ],
+              "privacy": "public"
+            },
+            {
+              "kind": "method",
+              "name": "setNumberPostProcessorForLocale",
+              "parameters": [
+                {
+                  "name": "{ locale, postProcessor }"
+                },
+                {
+                  "name": "options",
+                  "type": {
+                    "text": "{locale:string, postProcessor:NumberPostProcessor}"
+                  }
+                }
+              ],
+              "privacy": "public"
+            },
+            {
+              "kind": "method",
+              "name": "_setupTranslationToolSupport",
+              "description": "This value allows for support for Google Translate (or other 3rd parties taking control\nof the html[lang] attribute).\n\nHave the following scenario in mind:\n1. locale is initialized by developer via html[data-localize-lang=\"en-US\"] and\nhtml[lang=\"en-US\"]. When localize is loaded (note that this also can be after step 2 below),\nit will sync its initial state from html[data-localize-lang]\n2. Google Translate kicks in for the French language. It will set html[lang=\"fr\"].\nThis new language is not one known by us, so we most likely don't have translations for\nthis file. Therefore, we do NOT sync this value to LocalizeManager. The manager should\nstill ask for known resources (in this case for locale 'en-US')\n3. locale is changed (think of a language dropdown)\nIt's a bit of a weird case, because we would not expect an end user to do this. If he/she\ndoes, make sure that we do not go against Google Translate, so we maintain accessibility\n(by not altering html[lang]). We detect this by reading #localeSetByTranslationTool:\nwhen its value is null, we consider Google translate 'not active'.\n\nWhen Google Translate is turned off by the user (html[lang=auto]),\n`localize.locale` will be synced to html[lang] again\n\nKeep in mind that all of the above also works with other tools than Google Translate,\nbut this is the most widely used tool and therefore used as an example.",
+              "privacy": "protected"
+            },
+            {
+              "kind": "method",
+              "name": "_setHtmlLangAttribute",
+              "parameters": [
+                {
+                  "name": "locale",
+                  "type": {
+                    "text": "string"
+                  }
+                }
+              ],
+              "privacy": "protected"
+            },
             {
               "kind": "method",
               "name": "_setupHtmlLangAttributeObserver",
@@ -112333,7 +112754,7 @@
               ],
               "return": {
                 "type": {
-                  "text": "Promise.<Object|void>"
+                  "text": "Promise<Object|void>"
                 }
               },
               "privacy": "protected"
@@ -112396,7 +112817,7 @@
               ],
               "return": {
                 "type": {
-                  "text": "Promise.<any>"
+                  "text": "Promise<any>"
                 }
               },
               "privacy": "protected"
@@ -112420,7 +112841,7 @@
                 {
                   "name": "promise",
                   "type": {
-                    "text": "Promise.<Object|void>"
+                    "text": "Promise<Object|void>"
                   }
                 }
               ],
@@ -112462,69 +112883,6 @@
               },
               "privacy": "protected"
             },
-            {
-              "kind": "method",
-              "name": "addEventListener",
-              "parameters": [
-                {
-                  "name": "type",
-                  "type": {
-                    "text": "string"
-                  }
-                },
-                {
-                  "name": "listener",
-                  "type": {
-                    "text": "EventListener"
-                  }
-                },
-                {
-                  "name": "options",
-                  "type": {
-                    "text": "...Object"
-                  }
-                }
-              ],
-              "privacy": "public"
-            },
-            {
-              "kind": "method",
-              "name": "removeEventListener",
-              "parameters": [
-                {
-                  "name": "type",
-                  "type": {
-                    "text": "string"
-                  }
-                },
-                {
-                  "name": "listener",
-                  "type": {
-                    "text": "EventListener"
-                  }
-                },
-                {
-                  "name": "options",
-                  "type": {
-                    "text": "...Object"
-                  }
-                }
-              ],
-              "privacy": "public"
-            },
-            {
-              "kind": "method",
-              "name": "dispatchEvent",
-              "parameters": [
-                {
-                  "name": "event",
-                  "type": {
-                    "text": "CustomEvent"
-                  }
-                }
-              ],
-              "privacy": "public"
-            },
             {
               "kind": "method",
               "name": "_onLocaleChanged",
@@ -112618,61 +112976,28 @@
             },
             {
               "kind": "method",
-              "name": "setDatePostProcessorForLocale",
-              "parameters": [
-                {
-                  "name": "{ locale, postProcessor }"
-                },
-                {
-                  "name": "options",
-                  "type": {
-                    "text": "{locale:string, postProcessor:DatePostProcessor}"
-                  }
-                }
-              ],
-              "privacy": "public"
-            },
-            {
-              "kind": "method",
-              "name": "setNumberPostProcessorForLocale",
+              "name": "#assertCorrectLocale",
+              "privacy": "private",
               "parameters": [
                 {
-                  "name": "{ locale, postProcessor }"
-                },
-                {
-                  "name": "options",
+                  "name": "value",
                   "type": {
-                    "text": "{locale:string, postProcessor:NumberPostProcessor}"
+                    "text": "string"
                   }
                 }
-              ],
-              "privacy": "public"
-            },
-            {
-              "kind": "field",
-              "name": "__delegationTarget",
-              "privacy": "private"
-            },
-            {
-              "kind": "field",
-              "name": "_autoLoadOnLocaleChange",
-              "type": {
-                "text": "boolean"
-              },
-              "privacy": "protected",
-              "default": "!!autoLoadOnLocaleChange"
+              ]
             },
             {
               "kind": "field",
-              "name": "_fallbackLocale",
-              "privacy": "protected",
-              "default": "fallbackLocale"
+              "name": "_supportExternalTranslationTools",
+              "deprecated": "true",
+              "privacy": "protected"
             },
             {
               "kind": "field",
-              "name": "_showKeyAsFallback",
-              "privacy": "protected",
-              "default": "showKeyAsFallback"
+              "name": "_langAttrSetByTranslationTool",
+              "deprecated": "true",
+              "privacy": "protected"
             },
             {
               "kind": "field",
@@ -112682,62 +113007,24 @@
             },
             {
               "kind": "field",
-              "name": "__storage",
-              "type": {
-                "text": "Object.<string, Object.<string, Object>>"
-              },
-              "privacy": "private",
-              "default": "{}"
-            },
-            {
-              "kind": "field",
-              "name": "__namespacePatternsMap",
-              "type": {
-                "text": "Map.<RegExp|string, function>"
-              },
-              "privacy": "private",
-              "default": "new Map()"
-            },
-            {
-              "kind": "field",
-              "name": "__namespaceLoadersCache",
-              "type": {
-                "text": "Object.<string, function|null>"
-              },
-              "privacy": "private",
-              "default": "{}"
-            },
-            {
-              "kind": "field",
-              "name": "__namespaceLoaderPromisesCache",
-              "type": {
-                "text": "Object.<string, Object.<string, Promise.<Object|void>>>"
-              },
-              "privacy": "private",
-              "default": "{}"
-            },
-            {
-              "kind": "field",
-              "name": "formatNumberOptions",
+              "name": "_autoLoadOnLocaleChange",
               "type": {
-                "text": "object"
+                "text": "boolean"
               },
-              "default": "{ returnIfNaN: '', /** @type {Map<string,DatePostProcessor>} */ postProcessors: new Map(), }",
-              "privacy": "public"
+              "privacy": "protected",
+              "default": "!!autoLoadOnLocaleChange"
             },
             {
               "kind": "field",
-              "name": "formatDateOptions",
-              "type": {
-                "text": "object"
-              },
-              "default": "{ /** @type {Map<string,DatePostProcessor>} */ postProcessors: new Map(), }",
-              "privacy": "public"
+              "name": "_showKeyAsFallback",
+              "privacy": "protected",
+              "default": "showKeyAsFallback"
             },
             {
               "kind": "field",
-              "name": "_supportExternalTranslationTools",
-              "privacy": "protected"
+              "name": "_fallbackLocale",
+              "privacy": "protected",
+              "default": "fallbackLocale"
             }
           ],
           "events": [
@@ -112753,7 +113040,11 @@
                 "text": "CustomEvent"
               }
             }
-          ]
+          ],
+          "superclass": {
+            "name": "EventTarget",
+            "module": "components/localize/src/LocalizeManager.js"
+          }
         }
       ],
       "exports": [
@@ -114969,6 +115260,12 @@
               "name": "_teardownOpenCloseListeners",
               "privacy": "protected"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve"
+            },
             {
               "kind": "field",
               "name": "_overlayInvokerNode",
@@ -115289,6 +115586,16 @@
                 "module": "components/overlays/src/OverlayMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "OverlayMixin",
+                "module": "components/overlays/src/OverlayMixin.js"
+              }
+            },
             {
               "kind": "field",
               "name": "_overlayInvokerNode",
@@ -116137,6 +116444,13 @@
               },
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "privacy": "public"
+            },
             {
               "kind": "field",
               "name": "_progressPercentage",
@@ -118094,6 +118408,17 @@
                 "module": "components/form-core/src/FormControlMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "FormControlMixin",
+                "module": "components/form-core/src/FormControlMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -119201,7 +119526,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -120269,6 +120594,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -120894,7 +121230,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -121997,7 +122333,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -122827,7 +123163,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -122941,6 +123277,17 @@
                 "module": "components/overlays/src/OverlayMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionListbox",
+                "module": "components/listbox/src/LionListbox.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "field",
               "name": "_overlayReferenceNode",
@@ -126338,6 +126685,17 @@
               },
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionButton",
+                "module": "components/button/src/LionButton.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "__internalSetTabIndex",
@@ -126876,6 +127234,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -127507,7 +127876,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -129147,7 +129516,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -129477,7 +129846,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -129639,6 +130008,13 @@
               "readonly": true,
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_goTo",
@@ -129841,6 +130217,13 @@
               ],
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "privacy": "public"
+            },
             {
               "kind": "field",
               "name": "status",
@@ -130160,7 +130543,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -130918,6 +131301,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -131467,7 +131861,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -132849,7 +133243,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -133229,6 +133623,17 @@
               },
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "DisabledWithTabIndexMixin",
+                "module": "components/core/src/DisabledWithTabIndexMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "__internalSetTabIndex",
@@ -133445,6 +133850,13 @@
               "readonly": true,
               "privacy": "public"
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "__setupSlots",
@@ -134534,6 +134946,17 @@
                 "module": "components/form-core/src/LionField.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "LionField",
+                "module": "components/form-core/src/LionField.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_triggerInitialModelValueChangedEvent",
@@ -135149,7 +135572,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -136267,7 +136690,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -136511,7 +136934,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -136773,6 +137196,17 @@
           "description": "",
           "name": "LionTooltip",
           "members": [
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "OverlayMixin",
+                "module": "components/overlays/src/OverlayMixin.js"
+              },
+              "privacy": "public"
+            },
             {
               "kind": "method",
               "name": "_defineOverlayConfig",
@@ -138838,7 +139272,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "attribute": "allow-cross-root-registration",
               "inheritedFrom": {
@@ -139569,6 +140003,16 @@
                 "module": "components/form-core/src/InteractionStateMixin.js"
               }
             },
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "TODO: check if this is a false positive or if we can improve",
+              "inheritedFrom": {
+                "name": "InteractionStateMixin",
+                "module": "components/form-core/src/InteractionStateMixin.js"
+              }
+            },
             {
               "kind": "method",
               "name": "_enhanceLightDomClasses",
@@ -140372,7 +140816,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -140631,7 +141075,7 @@
               "type": {
                 "text": "boolean"
               },
-              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion-web.netlify.app/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
+              "description": "To encourage accessibility best practices, `form-element-register` events\ndo 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.\nUse this option if you know what you're doing. It will then be possible to nest FormControls\ninside shadow dom. See https://lion.js.org/fundamentals/rationales/accessibility/#shadow-roots-and-accessibility",
               "default": "false",
               "fieldName": "allowCrossRootRegistration",
               "inheritedFrom": {
@@ -141734,9 +142178,13 @@
       "kind": "javascript-module",
       "path": "components/core/src/ScopedElementsMixin.js",
       "declarations": [
+        {
+          "kind": "function",
+          "name": "supportsScopedRegistry"
+        },
         {
           "kind": "mixin",
-          "description": "",
+          "description": "This file is combination of '@open-wc/scoped-elements@v3/lit-element.js' and '@open-wc/scoped-elements@v3/html-element.js'.\nThen on top of those, some code from '@open-wc/scoped-elements@v2' is brought to to make polyfill not mandatory.\nThis can be a great help for ssr scenarios, allowing elements to be consumed without needing knowledge about internall\nconsumption.\n(N.B. at this point in time, this is limited to the scenario where there's one version of lion on the page).\n\n## Considerations\nIn its current state, the [scoped-custom-element-registry](https://github.com/webcomponents/polyfills/tree/master/packages/scoped-custom-element-registry) draft spec has uncertainties:\n- the spec is not yet final; it's not clear how long it will be dependent on a polyfill\n- the polyfill conflicts with new browser functionality (form-associated custom elements in Safari, ShadowRoot.createElement in Chrome Canary, etc.).\n- the spsc is not compatible with SSR and it remains unclear if it will be in the future\n\nAlso see: https://github.com/webcomponents/polyfills/issues?q=scoped-custom-element-registry\n\nIn previous considerations (last year), we betted on the spec to evolve quickly and the polyfill to be stable.\nTill this day, little progress has been made. In the meantime.",
           "name": "ScopedElementsMixin",
           "members": [
             {
@@ -141759,7 +142207,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }
@@ -141806,6 +142254,14 @@
         }
       ],
       "exports": [
+        {
+          "kind": "js",
+          "name": "supportsScopedRegistry",
+          "declaration": {
+            "name": "supportsScopedRegistry",
+            "module": "components/core/src/ScopedElementsMixin.js"
+          }
+        },
         {
           "kind": "js",
           "name": "ScopedElementsMixin",
@@ -141918,6 +142374,12 @@
           "description": "Why this mixin?\n- it adheres to the \"Member Order Independence\" web components standard:\nhttps://github.com/webcomponents/gold-standard/wiki/Member-Order-Independence\n- sync observers can be dependent on the outcome of the render function (or, more generically\nspeaking, the light and shadow dom). This aligns with the 'updated' callback that is supported\nout of the box by LitElement, which runs after connectedCallback as well.\n- makes the propertyAccessor.`hasChanged` compatible in synchronous updates:\n`updateSync` will only be called when new value differs from old value.\nSee: https://lit-element.polymer-project.org/guide/lifecycle#haschanged\n- it is a stable abstraction on top of a protected/non official lifecycle LitElement api.\nWhenever the implementation of `requestUpdate` changes (this happened in the past for\n`requestUpdate`) we only have to change our abstraction instead of all our components",
           "name": "SyncUpdatableMixin",
           "members": [
+            {
+              "kind": "field",
+              "name": "enabledWarnings",
+              "static": true,
+              "description": "// TODO: check if this is a false positive or if we can improve"
+            },
             {
               "kind": "method",
               "name": "__syncUpdatableHasChanged",
@@ -149404,7 +149866,7 @@
                   }
                 },
                 {
-                  "name": "klass",
+                  "name": "classToBeRegistered",
                   "type": {
                     "text": "typeof HTMLElement"
                   }