@vaadin/button 25.2.0-alpha8 → 25.2.0-alpha9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -75,7 +75,7 @@
75
75
  "type": {
76
76
  "text": "boolean"
77
77
  },
78
- "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```",
78
+ "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```",
79
79
  "attribute": "disabled"
80
80
  }
81
81
  ],
@@ -85,7 +85,7 @@
85
85
  "type": {
86
86
  "text": "boolean"
87
87
  },
88
- "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```",
88
+ "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```",
89
89
  "fieldName": "disabled"
90
90
  }
91
91
  ],
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vaadin/button",
3
- "version": "25.2.0-alpha8",
3
+ "version": "25.2.0-alpha9",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
@@ -35,19 +35,19 @@
35
35
  ],
36
36
  "dependencies": {
37
37
  "@open-wc/dedupe-mixin": "^1.3.0",
38
- "@vaadin/a11y-base": "25.2.0-alpha8",
39
- "@vaadin/component-base": "25.2.0-alpha8",
40
- "@vaadin/vaadin-themable-mixin": "25.2.0-alpha8",
38
+ "@vaadin/a11y-base": "25.2.0-alpha9",
39
+ "@vaadin/component-base": "25.2.0-alpha9",
40
+ "@vaadin/vaadin-themable-mixin": "25.2.0-alpha9",
41
41
  "lit": "^3.0.0"
42
42
  },
43
43
  "devDependencies": {
44
- "@vaadin/aura": "25.2.0-alpha8",
45
- "@vaadin/chai-plugins": "25.2.0-alpha8",
46
- "@vaadin/icon": "25.2.0-alpha8",
47
- "@vaadin/icons": "25.2.0-alpha8",
48
- "@vaadin/test-runner-commands": "25.2.0-alpha8",
44
+ "@vaadin/aura": "25.2.0-alpha9",
45
+ "@vaadin/chai-plugins": "25.2.0-alpha9",
46
+ "@vaadin/icon": "25.2.0-alpha9",
47
+ "@vaadin/icons": "25.2.0-alpha9",
48
+ "@vaadin/test-runner-commands": "25.2.0-alpha9",
49
49
  "@vaadin/testing-helpers": "^2.0.0",
50
- "@vaadin/vaadin-lumo-styles": "25.2.0-alpha8",
50
+ "@vaadin/vaadin-lumo-styles": "25.2.0-alpha9",
51
51
  "sinon": "^21.0.2"
52
52
  },
53
53
  "customElements": "custom-elements.json",
@@ -55,5 +55,5 @@
55
55
  "web-types.json",
56
56
  "web-types.lit.json"
57
57
  ],
58
- "gitHead": "2b82e20cdfc605b1187e9a24ae42869e1500ab68"
58
+ "gitHead": "a38a03e8a8be45821f39c14054c63634dafe08d0"
59
59
  }
@@ -55,16 +55,14 @@ import { ButtonMixin } from './vaadin-button-mixin.js';
55
55
  */
56
56
  declare class Button extends ButtonMixin(ElementMixin(ThemableMixin(HTMLElement))) {
57
57
  /**
58
- * When disabled, the button is rendered as "dimmed" and prevents all
59
- * user interactions (mouse and keyboard).
58
+ * When disabled, the button is rendered as "dimmed".
60
59
  *
61
- * Since disabled buttons are not focusable and cannot react to hover
62
- * events by default, it can cause accessibility issues by making them
63
- * entirely invisible to assistive technologies, and prevents the use
64
- * of Tooltips to explain why the action is not available. This can be
65
- * addressed by enabling the feature flag `accessibleDisabledButtons`,
60
+ * By default, disabled buttons are not focusable and don't react to hover.
61
+ * As a result, they are hidden from assistive technologies, and it's not
62
+ * possible to show a tooltip to explain why they are disabled. This can
63
+ * be addressed by enabling the feature flag `accessibleDisabledButtons`,
66
64
  * which makes disabled buttons focusable and hoverable, while still
67
- * preventing them from being triggered:
65
+ * preventing them from being activated:
68
66
  *
69
67
  * ```js
70
68
  * // Set before any button is attached to the DOM.
@@ -77,16 +77,14 @@ class Button extends ButtonMixin(ElementMixin(ThemableMixin(PolylitMixin(LumoInj
77
77
  static get properties() {
78
78
  return {
79
79
  /**
80
- * When disabled, the button is rendered as "dimmed" and prevents all
81
- * user interactions (mouse and keyboard).
80
+ * When disabled, the button is rendered as "dimmed".
82
81
  *
83
- * Since disabled buttons are not focusable and cannot react to hover
84
- * events by default, it can cause accessibility issues by making them
85
- * entirely invisible to assistive technologies, and prevents the use
86
- * of Tooltips to explain why the action is not available. This can be
87
- * addressed by enabling the feature flag `accessibleDisabledButtons`,
82
+ * By default, disabled buttons are not focusable and don't react to hover.
83
+ * As a result, they are hidden from assistive technologies, and it's not
84
+ * possible to show a tooltip to explain why they are disabled. This can
85
+ * be addressed by enabling the feature flag `accessibleDisabledButtons`,
88
86
  * which makes disabled buttons focusable and hoverable, while still
89
- * preventing them from being triggered:
87
+ * preventing them from being activated:
90
88
  *
91
89
  * ```js
92
90
  * // Set before any button is attached to the DOM.
package/web-types.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/web-types",
3
3
  "name": "@vaadin/button",
4
- "version": "25.2.0-alpha8",
4
+ "version": "25.2.0-alpha9",
5
5
  "description-markup": "markdown",
6
6
  "contributions": {
7
7
  "html": {
@@ -12,7 +12,7 @@
12
12
  "attributes": [
13
13
  {
14
14
  "name": "disabled",
15
- "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```",
15
+ "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```",
16
16
  "value": {
17
17
  "type": [
18
18
  "boolean",
@@ -37,7 +37,7 @@
37
37
  "properties": [
38
38
  {
39
39
  "name": "disabled",
40
- "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```",
40
+ "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```",
41
41
  "value": {
42
42
  "type": [
43
43
  "boolean",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/web-types",
3
3
  "name": "@vaadin/button",
4
- "version": "25.2.0-alpha8",
4
+ "version": "25.2.0-alpha9",
5
5
  "description-markup": "markdown",
6
6
  "framework": "lit",
7
7
  "framework-config": {
@@ -21,7 +21,7 @@
21
21
  "attributes": [
22
22
  {
23
23
  "name": "?disabled",
24
- "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```",
24
+ "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```",
25
25
  "value": {
26
26
  "kind": "expression"
27
27
  }