Bump tough-cookie from 4.1.2 to 4.1.4 in /packages/SystemUI/scripts/token_alignment #50
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}
Devices with OLED display suffer from status-bar's notification items and nagivation bar's software keys causing permanent burn-ins when used long-term. Moving all items in the area both horizontally and vertically workarounds this problem. This new feature can be enabled by setting config_statusBarBurnInProtection to true. The shifting interval can be configured with config_shift_interval. The default shifting interval is 60 seconds. Forward-ported to oreo-mr1. Change-Id: I8df1ebc8bc0f359fe5a6a1fe11aa6201237a7359 SystemUI: rework statusbar burn-in protection controller * Turns out that this controller was instantiated twice resulting in two timers running simultaneously which resulted in views to shift abruptly. Since the shift amount was too low it was not noticeable at all. So now we instantiate it once with all final dependencies and inject PhoneStatusBarView in fragment transaction. * Finalized many instance variables and a reference to the main handler is kept instead of creating new ones in each cycle * simplified / generalised the shift algorithm a bit so that it's easily configurable * added a callback to reload shift vars on screen density changes * additional changes: * use the same controller for navigation handle, saves some cpu time Signed-off-by: jhonboy121 <[email protected]> SystemUI: inject BurnInProtectionController Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: use the scoped SysUISingleton annotation SystemUI: BurnInProtectionController: rewrite in kotlin and improvements * ditched TimerTask in favor of coroutines Signed-off-by: jhonboy121 <[email protected]> [jhonboy121]: * adapted to A13 * use BurnInHelper util functions for calculating offset [ghostrider-reborn]: * use NavigationBarView directly instead of CentralSurfaces * rework timer and offset calculation logic SystemUI: Enable statusbar burn-in protection by default * AOSP already provides a config for burn-in protection so enable statusbar burn-in protection based on that * To forcefully disable it, set config_statusBarBurnInProtection to false Change-Id: I1a0b5c06ed6092153a35cb1cdc12b3b5e865ce8f SystemUI: BurnInProtectionController: offset less aggressively Change-Id: Ib37b0fde6edfc34cad8876d2e01ba4f37f323036 Signed-off-by: jhonboy121 <[email protected]> SystemUI: Make setNavigationBarView and setPhoneStatusBarView nullable * this fixes a potential npe on devices without navbar or statusbar Change-Id: Ia8e0ff844e24f67685ba20ac61a88d3256c9c648 Co-authored-by: jhonboy121 <[email protected]> Co-authored-by: Adithya R <[email protected]> Co-authored-by: Fabian Leutenegger <[email protected]> Change-Id: I067022d43d20f43760a192b43569c31316a5337a Signed-off-by: Adithya R <[email protected]>
Animations slow down the phone. Gotta go fast especially while wake-and-unlocking with capacitive fingerprint scanners. Like @ jesec said in LineageOS/android_frameworks_base@32244a3, OEMs have been doing this for years. Based on: Author: Rishawn <[email protected]> Date: Mon Jan 10 09:47:15 2022 +0530 SystemUI: Allow disabling ripple effect on unlock [1/2] neobuddy89: * Reverse logic. Enabled animation by default. Author: Nauval Rizky <[email protected]> Date: Wed Jan 19 08:31:56 2022 +0700 SystemUI: Fix method for disabling unlock ripple animation NotificationShadeWindowController's are not gracefully closed, which leads to top parts of the screen is being obscured by invisible shade window. And also, "ripple" is actually still exists due to lightRevealScrim are being started by onKeyguardFadingAwayChanged, which is not what user expect when they want to disable the effect. So in order to handle those cases, lets intercept it from the AuthRippleController instead. [palaych] With system settings we need to pass UserHandle.USER_CURRENT to make sure we are getting proper value. Change-Id: I85ab96368c8b0099700f3de18ba95ce63eaac443 Co-authored-by: Rishawn <[email protected]> Co-authored-by: Nauval Rizky <[email protected]> Change-Id: I12f152e2c62b22ec75bcf86591721de01ab39c70
On some devices, transition from AOD_PAUSED state (when display is turned off when the proximity sensor is covered) back into AOD state (when it is no longer covered), is broken and results in screen staying black until it is turned on using the power button. This can be worked around by switching the display into the ON state briefly (1 sec) before coming back into the DOZE_AOD state. Note that this does not enter the fully on state (lockscreen), the only visible change is in brightness. To enable this workaround, enable this in the device's SystemUI overlay: config_displayTurnsOnWhenResumingAod Change-Id: I05ebd5402c0789dd095ea5b0e1af6204d84c5a65
Squashed: SystemUI: Hide notification scrim background when entering split shade Change-Id: I191b9e17d85931f029657abecf9ed648d11e19ae [neobuddy89: Adapted for A14 QPR1] Signed-off-by: Pranav Vashi <[email protected]>
…or brightness curve" This reverts commit ed7e7e4. Change-Id: Idf19a5c6ba20257ee48557975f5536d0501e6ab6
…s slider Backlight values are already gamma corrected. Change-Id: I83b38a1334b8df156e4e53b06243c48d565be5d5 Co-authored-by: minaripenguin <[email protected]> Co-authored-by: Cosmin Tanislav <[email protected]>
Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) from 4.1.2 to 4.1.4. - [Release notes](https://github.com/salesforce/tough-cookie/releases) - [Changelog](https://github.com/salesforce/tough-cookie/blob/master/CHANGELOG.md) - [Commits](salesforce/tough-cookie@v4.1.2...v4.1.4) --- updated-dependencies: - dependency-name: tough-cookie dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
kawaaii
force-pushed
the
fifteen
branch
2 times, most recently
from
7ec1d1a to
82ec188
Compare
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 tough-cookie from 4.1.2 to 4.1.4.
Release notes
Sourced from tough-cookie's releases.
Commits
cacbc37Bump version to 4.1.4a48fb3aAdd tests for url validation50e69bfMerge pull request #261 from postmanlabs/fix/url-string-validation1253d58Merge pull request #409 from corvidism/validators-to-string238367eAdd local alias fortoString4ff4d294.1.3 release preparation, update the package and lib/version to 4.1.3. (#284)12d4747Prevent prototype pollution in cookie memstore (#283)f06b72dFix documentation for store.findCookies, missing allowSpecialUseDomain proper...cf6debdFix incorrect string validation for URLMaintainer changes
This version was pushed to npm by ccasey, a new releaser for tough-cookie since your current version.
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)You can disable automated security fix PRs for this repo from the Security Alerts page.