🚨 Latest Research:Tanstack npm Packages Compromised in Ongoing Mini Shai-Hulud Supply-Chain Attack.Learn More →
@vaadin/button
Advanced tools
@vaadin/button - npm Package Compare versions
@@ -78,3 +78,3 @@ { | ||
| }, | ||
| "description": "When disabled, the button is rendered as \"dimmed\" and prevents all\nuser interactions (mouse and keyboard).\n\nSince disabled buttons are not focusable and cannot react to hover\nevents by default, it can cause accessibility issues by making them\nentirely invisible to assistive technologies, and prevents the use\nof Tooltips to explain why the action is not available. This can be\naddressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being triggered:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "description": "When disabled, the button is rendered as \"dimmed\".\n\nBy default, disabled buttons are not focusable and don't react to hover.\nAs a result, they are hidden from assistive technologies, and it's not\npossible to show a tooltip to explain why they are disabled. This can\nbe addressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being activated:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "attribute": "disabled" | ||
@@ -89,3 +89,3 @@ } | ||
| }, | ||
| "description": "When disabled, the button is rendered as \"dimmed\" and prevents all\nuser interactions (mouse and keyboard).\n\nSince disabled buttons are not focusable and cannot react to hover\nevents by default, it can cause accessibility issues by making them\nentirely invisible to assistive technologies, and prevents the use\nof Tooltips to explain why the action is not available. This can be\naddressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being triggered:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "description": "When disabled, the button is rendered as \"dimmed\".\n\nBy default, disabled buttons are not focusable and don't react to hover.\nAs a result, they are hidden from assistive technologies, and it's not\npossible to show a tooltip to explain why they are disabled. This can\nbe addressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being activated:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "fieldName": "disabled" | ||
@@ -92,0 +92,0 @@ } |
+11
-11
| { | ||
| "name": "@vaadin/button", | ||
| "version": "25.2.0-alpha8", | ||
| "version": "25.2.0-alpha9", | ||
| "publishConfig": { | ||
@@ -38,15 +38,15 @@ "access": "public" | ||
| "@open-wc/dedupe-mixin": "^1.3.0", | ||
| "@vaadin/a11y-base": "25.2.0-alpha8", | ||
| "@vaadin/component-base": "25.2.0-alpha8", | ||
| "@vaadin/vaadin-themable-mixin": "25.2.0-alpha8", | ||
| "@vaadin/a11y-base": "25.2.0-alpha9", | ||
| "@vaadin/component-base": "25.2.0-alpha9", | ||
| "@vaadin/vaadin-themable-mixin": "25.2.0-alpha9", | ||
| "lit": "^3.0.0" | ||
| }, | ||
| "devDependencies": { | ||
| "@vaadin/aura": "25.2.0-alpha8", | ||
| "@vaadin/chai-plugins": "25.2.0-alpha8", | ||
| "@vaadin/icon": "25.2.0-alpha8", | ||
| "@vaadin/icons": "25.2.0-alpha8", | ||
| "@vaadin/test-runner-commands": "25.2.0-alpha8", | ||
| "@vaadin/aura": "25.2.0-alpha9", | ||
| "@vaadin/chai-plugins": "25.2.0-alpha9", | ||
| "@vaadin/icon": "25.2.0-alpha9", | ||
| "@vaadin/icons": "25.2.0-alpha9", | ||
| "@vaadin/test-runner-commands": "25.2.0-alpha9", | ||
| "@vaadin/testing-helpers": "^2.0.0", | ||
| "@vaadin/vaadin-lumo-styles": "25.2.0-alpha8", | ||
| "@vaadin/vaadin-lumo-styles": "25.2.0-alpha9", | ||
| "sinon": "^21.0.2" | ||
@@ -59,3 +59,3 @@ }, | ||
| ], | ||
| "gitHead": "2b82e20cdfc605b1187e9a24ae42869e1500ab68" | ||
| "gitHead": "a38a03e8a8be45821f39c14054c63634dafe08d0" | ||
| } |
@@ -58,12 +58,10 @@ /** | ||
| /** | ||
| * When disabled, the button is rendered as "dimmed" and prevents all | ||
| * user interactions (mouse and keyboard). | ||
| * When disabled, the button is rendered as "dimmed". | ||
| * | ||
| * Since disabled buttons are not focusable and cannot react to hover | ||
| * events by default, it can cause accessibility issues by making them | ||
| * entirely invisible to assistive technologies, and prevents the use | ||
| * of Tooltips to explain why the action is not available. This can be | ||
| * addressed by enabling the feature flag `accessibleDisabledButtons`, | ||
| * By default, disabled buttons are not focusable and don't react to hover. | ||
| * As a result, they are hidden from assistive technologies, and it's not | ||
| * possible to show a tooltip to explain why they are disabled. This can | ||
| * be addressed by enabling the feature flag `accessibleDisabledButtons`, | ||
| * which makes disabled buttons focusable and hoverable, while still | ||
| * preventing them from being triggered: | ||
| * preventing them from being activated: | ||
| * | ||
@@ -70,0 +68,0 @@ * ```js |
@@ -80,12 +80,10 @@ /** | ||
| /** | ||
| * When disabled, the button is rendered as "dimmed" and prevents all | ||
| * user interactions (mouse and keyboard). | ||
| * When disabled, the button is rendered as "dimmed". | ||
| * | ||
| * Since disabled buttons are not focusable and cannot react to hover | ||
| * events by default, it can cause accessibility issues by making them | ||
| * entirely invisible to assistive technologies, and prevents the use | ||
| * of Tooltips to explain why the action is not available. This can be | ||
| * addressed by enabling the feature flag `accessibleDisabledButtons`, | ||
| * By default, disabled buttons are not focusable and don't react to hover. | ||
| * As a result, they are hidden from assistive technologies, and it's not | ||
| * possible to show a tooltip to explain why they are disabled. This can | ||
| * be addressed by enabling the feature flag `accessibleDisabledButtons`, | ||
| * which makes disabled buttons focusable and hoverable, while still | ||
| * preventing them from being triggered: | ||
| * preventing them from being activated: | ||
| * | ||
@@ -92,0 +90,0 @@ * ```js |
+3
-3
| { | ||
| "$schema": "https://json.schemastore.org/web-types", | ||
| "name": "@vaadin/button", | ||
| "version": "25.2.0-alpha8", | ||
| "version": "25.2.0-alpha9", | ||
| "description-markup": "markdown", | ||
@@ -15,3 +15,3 @@ "contributions": { | ||
| "name": "disabled", | ||
| "description": "When disabled, the button is rendered as \"dimmed\" and prevents all\nuser interactions (mouse and keyboard).\n\nSince disabled buttons are not focusable and cannot react to hover\nevents by default, it can cause accessibility issues by making them\nentirely invisible to assistive technologies, and prevents the use\nof Tooltips to explain why the action is not available. This can be\naddressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being triggered:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "description": "When disabled, the button is rendered as \"dimmed\".\n\nBy default, disabled buttons are not focusable and don't react to hover.\nAs a result, they are hidden from assistive technologies, and it's not\npossible to show a tooltip to explain why they are disabled. This can\nbe addressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being activated:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "value": { | ||
@@ -41,3 +41,3 @@ "type": [ | ||
| "name": "disabled", | ||
| "description": "When disabled, the button is rendered as \"dimmed\" and prevents all\nuser interactions (mouse and keyboard).\n\nSince disabled buttons are not focusable and cannot react to hover\nevents by default, it can cause accessibility issues by making them\nentirely invisible to assistive technologies, and prevents the use\nof Tooltips to explain why the action is not available. This can be\naddressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being triggered:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "description": "When disabled, the button is rendered as \"dimmed\".\n\nBy default, disabled buttons are not focusable and don't react to hover.\nAs a result, they are hidden from assistive technologies, and it's not\npossible to show a tooltip to explain why they are disabled. This can\nbe addressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being activated:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "value": { | ||
@@ -44,0 +44,0 @@ "type": [ |
| { | ||
| "$schema": "https://json.schemastore.org/web-types", | ||
| "name": "@vaadin/button", | ||
| "version": "25.2.0-alpha8", | ||
| "version": "25.2.0-alpha9", | ||
| "description-markup": "markdown", | ||
@@ -24,3 +24,3 @@ "framework": "lit", | ||
| "name": "?disabled", | ||
| "description": "When disabled, the button is rendered as \"dimmed\" and prevents all\nuser interactions (mouse and keyboard).\n\nSince disabled buttons are not focusable and cannot react to hover\nevents by default, it can cause accessibility issues by making them\nentirely invisible to assistive technologies, and prevents the use\nof Tooltips to explain why the action is not available. This can be\naddressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being triggered:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "description": "When disabled, the button is rendered as \"dimmed\".\n\nBy default, disabled buttons are not focusable and don't react to hover.\nAs a result, they are hidden from assistive technologies, and it's not\npossible to show a tooltip to explain why they are disabled. This can\nbe addressed by enabling the feature flag `accessibleDisabledButtons`,\nwhich makes disabled buttons focusable and hoverable, while still\npreventing them from being activated:\n\n```js\n// Set before any button is attached to the DOM.\nwindow.Vaadin.featureFlags.accessibleDisabledButtons = true\n```", | ||
| "value": { | ||
@@ -27,0 +27,0 @@ "kind": "expression" |
New alerts
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Fixed alerts
Long strings
Supply chain riskContains long string literals, which may be a sign of obfuscated or packed code.
Found 1 instance in 1 package
Worsened metrics
- Total package byte prevSize
42101
-1.87%- Lines of code
673
-0.59%Dependency changes
+ Added
@vaadin/a11y-base@25.2.0-alpha9(transitive)+ Added
@vaadin/component-base@25.2.0-alpha9(transitive)+ Added
@vaadin/vaadin-themable-mixin@25.2.0-alpha9(transitive)- Removed
@vaadin/a11y-base@25.2.0-alpha8(transitive)- Removed
@vaadin/component-base@25.2.0-alpha8(transitive)- Removed
@vaadin/vaadin-themable-mixin@25.2.0-alpha8(transitive)