Bump @types/react-color from 3.0.6 to 3.0.7 #814
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [@types/react-color](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/react-color) from 3.0.6 to 3.0.7. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/react-color) --- updated-dependencies: - dependency-name: "@types/react-color" dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
|
Superseded by #818. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/types/react-color-3.0.7
branch
CryZe
added a commit
to CryZe/LiveSplitOne
that referenced
this pull request
Jun 9, 2024
Every browser's `performance.now()` implementation is not spec compliant, unless the browser is running on Windows. On every other operating system, `performance.now()` does not properly keep ticking while the operating system is suspended / sleeping. There isn't much that we can do. What we can do is we calculate the initial difference between `performance.now()` and `Date.now()` and store it in a thread local. Later, when the phone gets locked, `performance.now()` starts to break. However, we can detect when the phone gets unlocked again by listening to the `visibilitychange` event. This is where we can update the difference again. This of course isn't ideal, as `Date.now()` gets adjusted by NTP synchronizations, but it's the best we can do. More information: https://developer.mozilla.org/en-US/docs/Web/API/Performance/now#ticking_during_sleep https://www.igvita.com/2015/11/20/dont-lose-user-and-app-state-use-page-visibility/
CryZe
added a commit
that referenced
this pull request
Jun 9, 2024
Every browser's `performance.now()` implementation is not spec compliant, unless the browser is running on Windows. On every other operating system, `performance.now()` does not properly keep ticking while the operating system is suspended / sleeping. There isn't much that we can do. What we can do is we calculate the initial difference between `performance.now()` and `Date.now()` and store it in a thread local. Later, when the phone gets locked, `performance.now()` starts to break. However, we can detect when the phone gets unlocked again by listening to the `visibilitychange` event. This is where we can update the difference again. This of course isn't ideal, as `Date.now()` gets adjusted by NTP synchronizations, but it's the best we can do. More information: https://developer.mozilla.org/en-US/docs/Web/API/Performance/now#ticking_during_sleep https://www.igvita.com/2015/11/20/dont-lose-user-and-app-state-use-page-visibility/
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps @types/react-color from 3.0.6 to 3.0.7.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)