@vaadin/integer-field 24.9.0-alpha2 → 24.9.0-beta2

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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vaadin/integer-field",
3
- "version": "24.9.0-alpha2",
3
+ "version": "24.9.0-beta2",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },
@@ -35,14 +35,14 @@
35
35
  ],
36
36
  "dependencies": {
37
37
  "@polymer/polymer": "^3.0.0",
38
- "@vaadin/component-base": "24.9.0-alpha2",
39
- "@vaadin/number-field": "24.9.0-alpha2",
40
- "@vaadin/vaadin-lumo-styles": "24.9.0-alpha2",
41
- "@vaadin/vaadin-material-styles": "24.9.0-alpha2"
38
+ "@vaadin/component-base": "24.9.0-beta2",
39
+ "@vaadin/number-field": "24.9.0-beta2",
40
+ "@vaadin/vaadin-lumo-styles": "24.9.0-beta2",
41
+ "@vaadin/vaadin-material-styles": "24.9.0-beta2"
42
42
  },
43
43
  "devDependencies": {
44
- "@vaadin/chai-plugins": "24.9.0-alpha2",
45
- "@vaadin/test-runner-commands": "24.9.0-alpha2",
44
+ "@vaadin/chai-plugins": "24.9.0-beta2",
45
+ "@vaadin/test-runner-commands": "24.9.0-beta2",
46
46
  "@vaadin/testing-helpers": "^1.1.0",
47
47
  "sinon": "^18.0.0"
48
48
  },
@@ -50,5 +50,5 @@
50
50
  "web-types.json",
51
51
  "web-types.lit.json"
52
52
  ],
53
- "gitHead": "dd99dece1b54942ab0e421892b089e506822c5f5"
53
+ "gitHead": "cf8def153fcf724b305f9ad823dc9af27e31ad07"
54
54
  }
@@ -55,15 +55,34 @@ export interface IntegerFieldEventMap extends HTMLElementEventMap, IntegerFieldC
55
55
  *
56
56
  * ### Styling
57
57
  *
58
- * `<vaadin-integer-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.
59
- * See [`<vaadin-text-field>`](#/elements/vaadin-text-field) for the styling documentation.
58
+ * The following shadow DOM parts are available for styling:
60
59
  *
61
- * In addition to `<vaadin-text-field>` parts, the following parts are available for theming:
60
+ * Part name | Description
61
+ * ---------------------|----------------
62
+ * `label` | The label element
63
+ * `input-field` | The element that wraps prefix, value and suffix
64
+ * `clear-button` | The clear button
65
+ * `error-message` | The error message element
66
+ * `helper-text` | The helper text element wrapper
67
+ * `required-indicator` | The `required` state indicator element
68
+ * `increase-button` | Increase ("plus") button
69
+ * `decrease-button` | Decrease ("minus") button
62
70
  *
63
- * Part name | Description
64
- * ------------------|-------------------------
65
- * `increase-button` | Increase ("plus") button
66
- * `decrease-button` | Decrease ("minus") button
71
+ * The following state attributes are available for styling:
72
+ *
73
+ * Attribute | Description
74
+ * ---------------------|---------------------------------
75
+ * `disabled` | Set when the element is disabled
76
+ * `has-value` | Set when the element has a value
77
+ * `has-label` | Set when the element has a label
78
+ * `has-helper` | Set when the element has helper text or slot
79
+ * `has-error-message` | Set when the element has an error message
80
+ * `has-tooltip` | Set when the element has a slotted tooltip
81
+ * `invalid` | Set when the element is invalid
82
+ * `input-prevented` | Temporarily set when invalid input is prevented
83
+ * `focused` | Set when the element is focused
84
+ * `focus-ring` | Set when the element is keyboard focused
85
+ * `readonly` | Set when the element is readonly
67
86
  *
68
87
  * See [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.
69
88
  *
@@ -15,15 +15,34 @@ import { NumberField } from '@vaadin/number-field/src/vaadin-number-field.js';
15
15
  *
16
16
  * ### Styling
17
17
  *
18
- * `<vaadin-integer-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.
19
- * See [`<vaadin-text-field>`](#/elements/vaadin-text-field) for the styling documentation.
18
+ * The following shadow DOM parts are available for styling:
20
19
  *
21
- * In addition to `<vaadin-text-field>` parts, the following parts are available for theming:
20
+ * Part name | Description
21
+ * ---------------------|----------------
22
+ * `label` | The label element
23
+ * `input-field` | The element that wraps prefix, value and suffix
24
+ * `clear-button` | The clear button
25
+ * `error-message` | The error message element
26
+ * `helper-text` | The helper text element wrapper
27
+ * `required-indicator` | The `required` state indicator element
28
+ * `increase-button` | Increase ("plus") button
29
+ * `decrease-button` | Decrease ("minus") button
22
30
  *
23
- * Part name | Description
24
- * ------------------|-------------------------
25
- * `increase-button` | Increase ("plus") button
26
- * `decrease-button` | Decrease ("minus") button
31
+ * The following state attributes are available for styling:
32
+ *
33
+ * Attribute | Description
34
+ * ---------------------|---------------------------------
35
+ * `disabled` | Set when the element is disabled
36
+ * `has-value` | Set when the element has a value
37
+ * `has-label` | Set when the element has a label
38
+ * `has-helper` | Set when the element has helper text or slot
39
+ * `has-error-message` | Set when the element has an error message
40
+ * `has-tooltip` | Set when the element has a slotted tooltip
41
+ * `invalid` | Set when the element is invalid
42
+ * `input-prevented` | Temporarily set when invalid input is prevented
43
+ * `focused` | Set when the element is focused
44
+ * `focus-ring` | Set when the element is keyboard focused
45
+ * `readonly` | Set when the element is readonly
27
46
  *
28
47
  * See [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.
29
48
  *
package/web-types.json CHANGED
@@ -1,14 +1,14 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/web-types",
3
3
  "name": "@vaadin/integer-field",
4
- "version": "24.9.0-alpha2",
4
+ "version": "24.9.0-beta2",
5
5
  "description-markup": "markdown",
6
6
  "contributions": {
7
7
  "html": {
8
8
  "elements": [
9
9
  {
10
10
  "name": "vaadin-integer-field",
11
- "description": "`<vaadin-integer-field>` is an input field web component that only accepts entering integer numbers.\n\n```html\n<vaadin-integer-field label=\"X\"></vaadin-integer-field>\n```\n\n### Styling\n\n`<vaadin-integer-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.\nSee [`<vaadin-text-field>`](https://cdn.vaadin.com/vaadin-web-components/24.9.0-alpha2/#/elements/vaadin-text-field) for the styling documentation.\n\nIn addition to `<vaadin-text-field>` parts, the following parts are available for theming:\n\nPart name | Description\n------------------|-------------------------\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change | Event\n:------------------------|:------------------\nempty => parsable | change\nempty => unparsable | unparsable-change\nparsable => empty | change\nparsable => parsable | change\nparsable => unparsable | change\nunparsable => empty | unparsable-change\nunparsable => parsable | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
11
+ "description": "`<vaadin-integer-field>` is an input field web component that only accepts entering integer numbers.\n\n```html\n<vaadin-integer-field label=\"X\"></vaadin-integer-field>\n```\n\n### Styling\n\nThe following shadow DOM parts are available for styling:\n\nPart name | Description\n---------------------|----------------\n`label` | The label element\n`input-field` | The element that wraps prefix, value and suffix\n`clear-button` | The clear button\n`error-message` | The error message element\n`helper-text` | The helper text element wrapper\n`required-indicator` | The `required` state indicator element\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nThe following state attributes are available for styling:\n\nAttribute | Description\n---------------------|---------------------------------\n`disabled` | Set when the element is disabled\n`has-value` | Set when the element has a value\n`has-label` | Set when the element has a label\n`has-helper` | Set when the element has helper text or slot\n`has-error-message` | Set when the element has an error message\n`has-tooltip` | Set when the element has a slotted tooltip\n`invalid` | Set when the element is invalid\n`input-prevented` | Temporarily set when invalid input is prevented\n`focused` | Set when the element is focused\n`focus-ring` | Set when the element is keyboard focused\n`readonly` | Set when the element is readonly\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change | Event\n:------------------------|:------------------\nempty => parsable | change\nempty => unparsable | unparsable-change\nparsable => empty | change\nparsable => parsable | change\nparsable => unparsable | change\nunparsable => empty | unparsable-change\nunparsable => parsable | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
12
12
  "attributes": [
13
13
  {
14
14
  "name": "disabled",
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/web-types",
3
3
  "name": "@vaadin/integer-field",
4
- "version": "24.9.0-alpha2",
4
+ "version": "24.9.0-beta2",
5
5
  "description-markup": "markdown",
6
6
  "framework": "lit",
7
7
  "framework-config": {
@@ -16,7 +16,7 @@
16
16
  "elements": [
17
17
  {
18
18
  "name": "vaadin-integer-field",
19
- "description": "`<vaadin-integer-field>` is an input field web component that only accepts entering integer numbers.\n\n```html\n<vaadin-integer-field label=\"X\"></vaadin-integer-field>\n```\n\n### Styling\n\n`<vaadin-integer-field>` provides the same set of shadow DOM parts and state attributes as `<vaadin-text-field>`.\nSee [`<vaadin-text-field>`](https://cdn.vaadin.com/vaadin-web-components/24.9.0-alpha2/#/elements/vaadin-text-field) for the styling documentation.\n\nIn addition to `<vaadin-text-field>` parts, the following parts are available for theming:\n\nPart name | Description\n------------------|-------------------------\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change | Event\n:------------------------|:------------------\nempty => parsable | change\nempty => unparsable | unparsable-change\nparsable => empty | change\nparsable => parsable | change\nparsable => unparsable | change\nunparsable => empty | unparsable-change\nunparsable => parsable | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
19
+ "description": "`<vaadin-integer-field>` is an input field web component that only accepts entering integer numbers.\n\n```html\n<vaadin-integer-field label=\"X\"></vaadin-integer-field>\n```\n\n### Styling\n\nThe following shadow DOM parts are available for styling:\n\nPart name | Description\n---------------------|----------------\n`label` | The label element\n`input-field` | The element that wraps prefix, value and suffix\n`clear-button` | The clear button\n`error-message` | The error message element\n`helper-text` | The helper text element wrapper\n`required-indicator` | The `required` state indicator element\n`increase-button` | Increase (\"plus\") button\n`decrease-button` | Decrease (\"minus\") button\n\nThe following state attributes are available for styling:\n\nAttribute | Description\n---------------------|---------------------------------\n`disabled` | Set when the element is disabled\n`has-value` | Set when the element has a value\n`has-label` | Set when the element has a label\n`has-helper` | Set when the element has helper text or slot\n`has-error-message` | Set when the element has an error message\n`has-tooltip` | Set when the element has a slotted tooltip\n`invalid` | Set when the element is invalid\n`input-prevented` | Temporarily set when invalid input is prevented\n`focused` | Set when the element is focused\n`focus-ring` | Set when the element is keyboard focused\n`readonly` | Set when the element is readonly\n\nSee [Styling Components](https://vaadin.com/docs/latest/styling/styling-components) documentation.\n\n### Change events\n\nDepending on the nature of the value change that the user attempts to commit e.g. by pressing Enter,\nthe component can fire either a `change` event or an `unparsable-change` event:\n\nValue change | Event\n:------------------------|:------------------\nempty => parsable | change\nempty => unparsable | unparsable-change\nparsable => empty | change\nparsable => parsable | change\nparsable => unparsable | change\nunparsable => empty | unparsable-change\nunparsable => parsable | change\nunparsable => unparsable | -\n\nNote, there is currently no way to detect unparsable => unparsable changes because the browser\ndoesn't provide access to unparsable values of native [type=number] inputs.",
20
20
  "extension": true,
21
21
  "attributes": [
22
22
  {