arrow-key-navigation - npm Package Compare versions

Comparing version 1.0.2 to 1.1.0

dist-node/index.js

@@ -13,3 +13,3 @@ 'use strict';
 // https://github.com/edenspiekermann/a11y-dialog/blob/cf4ed81/a11y-dialog.js#L6-L18
-var focusablesQuery = 'a[href], area[href], input, select, textarea, ' + 'button, iframe, object, embed, [contenteditable], [tabindex], video[controls], audio[controls]'; // TODO: email/number types are a special type, in that they return selectionStart/selectionEnd as null
+var focusablesQuery = 'a[href], area[href], input, select, textarea, ' + 'button, iframe, object, embed, [contenteditable], [tabindex], ' + 'video[controls], audio[controls], summary'; // TODO: email/number types are a special type, in that they return selectionStart/selectionEnd as null
 // As far as I can tell, there is no way to actually get the caret position from these inputs. So we
@@ -16,0 +16,0 @@ // don't do the proper caret handling for those inputs, unfortunately.

dist-src/index.js

@@ -9,3 +9,4 @@ /**
 var focusablesQuery = 'a[href], area[href], input, select, textarea, ' +
-    'button, iframe, object, embed, [contenteditable], [tabindex], video[controls], audio[controls]';
+    'button, iframe, object, embed, [contenteditable], [tabindex], ' +
+    'video[controls], audio[controls], summary';
 // TODO: email/number types are a special type, in that they return selectionStart/selectionEnd as null
@@ -12,0 +13,0 @@ // As far as I can tell, there is no way to actually get the caret position from these inputs. So we

dist-web/index.js

@@ -9,3 +9,4 @@ /**
 var focusablesQuery = 'a[href], area[href], input, select, textarea, ' +
-    'button, iframe, object, embed, [contenteditable], [tabindex], video[controls], audio[controls]';
+    'button, iframe, object, embed, [contenteditable], [tabindex], ' +
+    'video[controls], audio[controls], summary';
 // TODO: email/number types are a special type, in that they return selectionStart/selectionEnd as null
@@ -12,0 +13,0 @@ // As far as I can tell, there is no way to actually get the caret position from these inputs. So we

package.json

 {
   "name": "arrow-key-navigation",
   "description": "Add left/right key navigation to a KaiOS app or web app",
-  "version": "1.0.2",
+  "version": "1.1.0",
   "license": "Apache-2.0",
@@ -35,2 +35,3 @@ "files": [
     "@pika/plugin-build-node": "^0.7.1",
+    "@pika/plugin-build-umd": "^0.7.1",
     "@pika/plugin-build-web": "^0.7.1",
@@ -50,3 +51,4 @@ "@pika/plugin-ts-standard-pkg": "^0.7.1",
   "main": "dist-node/index.js",
-  "module": "dist-web/index.js"
+  "module": "dist-web/index.js",
+  "umd:main": "dist-umd/index.js"
 }

README.md

@@ -20,2 +20,4 @@ arrow-key-navigation [![Build Status](https://travis-ci.org/nolanlawson/arrow-key-navigation.svg)](https://travis-ci.org/nolanlawson/arrow-key-navigation)
 
+Or [browse unpkg.com](https://unpkg.com/browse/arrow-key-navigation/) for a list of build files.
+
 ## Usage
@@ -75,1 +77,7 @@
     npm test
+
+### Manual KaiOS app test
+
+The `index.html` and `manifest.webapp` files are designed for a quick-and-dirty KaiOS app test.
+
+Run `npm run build` and then install the root directory as a packaged KaiOS app to test it.

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

68643

increased by33.98%

Number of package files

11

increased by22.22%

Lines of code

615

increased by32.83%

Number of lines in readme file

82

increased by10.81%

Worsened metrics

Dev dependency count

13

increased by8.33%

No dependency changes