You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-53
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,5 @@
1
-
[](https://www.webcomponents.org/element/fooloomanzoo/color-picker)
[](https://www.npmjs.com/package/@fooloomanzoo/color-picker)
2
+
[](https://www.webcomponents.org/element/@fooloomanzoo/color-picker)
4
3
[](https://vaadin.com/directory/component/fooloomanzoocolor-picker)
5
4
6
5
_[Demo and API docs](https://fooloomanzoo.github.io/color-picker/components/color-picker/)_
@@ -14,7 +13,7 @@ _[Demo and API docs](https://fooloomanzoo.github.io/color-picker/components/colo
14
13
15
14
Internally it tests the browser, if native input-type `color` is supported. You can decide to use the native or the replacements during runtime. `color-element` can also be used separately. By default, the polyfilled version is used.
16
15
17
-
It might be useful for you to use, if you like to keep the native approach of Browsers on Mobile Devices, or you like to have a different look or you would like to have a guaranteed working **color-picker**. Another use case could be for example, if you want on _mobile devices_ use the native picker, when supported, and on _desktop devices_ this polyfill.
16
+
It might be useful for you to use, if you like to keep the native approach of Browsers on Mobile Devices, or you like to have a different look or you would like to have a guaranteed working **color-picker**. Another use case could be for example, if you want on _mobile devices_ use the native picker, when supported, and on _desktop devices_ this polyfill.
18
17
19
18
For that purposes the attributes **native** and **native-on-mobile** are provided.
20
19
@@ -30,28 +29,6 @@ The **[component page](https://fooloomanzoo.github.io/color-picker/components/co
0 commit comments