-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Throw InsecureContextError
if window.crypto.subtle
is undefined
#6487
Throw InsecureContextError
if window.crypto.subtle
is undefined
#6487
Conversation
…ndefined-is-not-a-constructor-or-null
…ndefined-is-not-a-constructor-or-null
…ndefined-is-not-a-constructor-or-null
…ndefined-is-not-a-constructor-or-null
…ndefined-is-not-a-constructor-or-null
…ndefined-is-not-a-constructor-or-null
…ndefined-is-not-a-constructor-or-null
(fix: `value "..." at "/0" must pass "bytes" validation`)
InsecureContextError
if window.crypto.subtle is undefined
InsecureContextError
if window.crypto.subtle
is undefined
Bundle StatsHey there, this message comes from a github action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Deploying with Cloudflare Pages
|
…s-not-a-constructor-or-null' into 6393-web3validatorerror-error-value-at-0-must-pass-bytes-validation
…s-not-a-constructor-or-null' into 6485-throw-insecurecontexterror-if-window.crypto.subtle-is-undefined
…s-validation' into 6485-throw-insecurecontexterror-if-window.crypto.subtle-is-undefined
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## 4.x #6487 +/- ##
=======================================
Coverage 91.01% 91.01%
=======================================
Files 214 214
Lines 8121 8134 +13
Branches 2174 2182 +8
=======================================
+ Hits 7391 7403 +12
- Misses 730 731 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not in favor of using jsdom for browser testing, as it already need many changes in our lib. jest + jsdom is direction that we will not go.
So we should use cypress for browser testing for now.
so if using a testing env is causing changes in code to be tested, thn it should be avoided. and in case of requirement of SSL, I think thats ok. |
Sounds good. However, the case that this PR is handling does not show in the browser for local addresses. So, it would not happen with our Cypress configuration. It happens only with remote Urls that is also not secure (http and not with https). And this case is simulated in jsdom currently. |
…pto.subtle-is-undefined
…pto.subtle-is-undefined
…pto.subtle-is-undefined
…pto.subtle-is-undefined
…pto.subtle-is-undefined
…pto.subtle-is-undefined
…pto.subtle-is-undefined
…pto.subtle-is-undefined
…pto.subtle-is-undefined
This PR has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment. |
Description
Fixes #6485
Type of change
Checklist:
npm run lint
with success and extended the tests and types if necessary.npm run test:unit
with success.npm run test:coverage
and my test cases cover all the lines and branches of the added code.npm run build
and testeddist/web3.min.js
in a browser.CHANGELOG.md
file in the root folder.