react-focus-lock - npm Package Compare versions

Comparing version 1.10.0 to 1.11.0

package.json

 {
   "name": "react-focus-lock",
-  "version": "1.10.0",
+  "version": "1.11.0",
   "description": "It is a trap! (for a focus)",
@@ -74,3 +74,3 @@ "main": "dist/index.js",
   "dependencies": {
-    "focus-lock": "^0.2.4",
+    "focus-lock": "^0.3.0",
     "prop-types": "^15.0.0",
@@ -77,0 +77,0 @@ "react-side-effect": "^1.1.3"

README.md

@@ -47,4 +47,7 @@ <div align="left">
 ```
-Demo - https://codesandbox.io/s/5wmrwlvxv4. To be honest - you dont need that demo. Focus lock just works. Always.
+Demo - https://codesandbox.io/s/5wmrwlvxv4.
 
+That is actually not enough, as long it is better to "shadow" rest of the page, to make it unclickable or
+unscrollable. And there is [react-locky](https://github.com/theKashey/react-locky) to do this job.
+
 # WHY?
@@ -51,0 +54,0 @@ From [MDN Article about accessible dialogs](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_dialog_role):

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

70103

increased by0.19%

Number of lines in readme file

150

increased by2.04%

Dependency changes

• + Addedfocus-lock@0.3.0(transitive)

• - Removedfocus-lock@0.2.4(transitive)

• Updatedfocus-lock@^0.3.0