AlexeyBarabash
AlexeyBarabash
Resolves https://github.com/brave/brave-browser/issues/24671 Small PR to deny resize of texarea for sync code ## Submitter Checklist: - [x] I confirm that no security/privacy review [is needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have [requested](https://github.com/brave/security/issues/new/choose)...
Resolves https://github.com/brave/brave-browser/issues/24121 This PR does 4 things: 1. Improvement of `TimeLimitedWords::GenerateForDate` / `TimeLimitedWords::Parse`. Now it returns base::expected result. This prevents the crash mentioned in issue and increases readability. 2. brave://sync-internals...
Resolves https://github.com/brave/brave-browser/issues/22884 ## Submitter Checklist: - [ ] I confirm that no security/privacy review [is needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have [requested](https://github.com/brave/security/issues/new/choose) one - [ ] There is a [ticket](https://github.com/brave/brave-browser/issues) for...
Revert of https://github.com/brave/sync/pull/363 as it is merged into staging and not into master and will not be fixed and uplifted to master as moving to sync v2
From the conversation with @bridiver and @darkdh. brianjohnson We need versioned deployments. Each server update uses a different url/lamda function and then those updated urls will just ride the release...
From @bridiver comment https://github.com/brave/sync/pull/226#discussion_r224933820 we should handle the case where all 3 are blank (first node added) - we really have no use or need for the base order in...
This PR changes some settings names by proposition from design team. Resolves https://github.com/brave/brave-browser/issues/26028 ## Submitter Checklist: - [x] I confirm that no security/privacy review [is needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have...
when server is about to reach max object limit on the client. Must not be merged as-is.
This is a follow-up for https://github.com/brave/go-sync/pull/176 . Client's PR https://github.com/brave/brave-core/pull/20329 sends in `HistoryDeleteDirectiveSpecifics` in un-encrypted way. Server should remove entries by `HistoryDeleteDirectiveSpecifics::global_id_directive::global_id` converted to `client_hash_tag` or by `HistoryDeleteDirectiveSpecifics::time_range_directive`. When this...
Resolves https://github.com/brave/brave-browser/issues/37725 This PR does two things: - displays Sync code expiry when showing the pairing codes, as the parent issue describes; - adjusts colors of Brave Sync screens on...