Skip to content
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

Set load flags to prevent reading from HTTP cache #8533

Merged
merged 1 commit into from
Apr 20, 2021

Conversation

yachtcaptain23
Copy link
Contributor

@yachtcaptain23 yachtcaptain23 commented Apr 14, 2021

Will now show the channel as not verified with this patch if there's no connection.

Before patch:
before_patch

After patch:
after_patch

Resolves brave/brave-browser#15154

Submitter Checklist:

  • I confirm that no security/privacy review is needed, or that I have requested one
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

On all OS's, please visit yachtcaptain23.github.io or another Rewards connected domain and make sure the Rewards check mark appears. Then disable the WiFi/internet connection and click refresh, and please observer that the Rewards check mark does not appear (or it says it's not verified)

@yachtcaptain23 yachtcaptain23 marked this pull request as ready for review April 19, 2021 00:31
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, would just add a test plan to the PR - thanks!

@yachtcaptain23 yachtcaptain23 merged commit ee553c3 into master Apr 20, 2021
@yachtcaptain23 yachtcaptain23 deleted the issues/15154 branch April 20, 2021 00:43
@emerick emerick added this to the 1.25.x - Nightly milestone Apr 20, 2021
kylehickinson pushed a commit that referenced this pull request Jan 4, 2024
* Refactor `SwapTransactionConfirmationView` into `SaferSignTransactionContainerView` & `SaferSignTransactionView`, remove dependency on `ParsedTransaction` for re-use by Sign panel.

* Add SaferSignMessageRequestContainerView & `SignMessageRequestStore` for Safer Sign CoW swaps in Signature Requests.

* Refactor `SignMessageRequestContentView` out of `SignMessageRequestView` for re-use. Update `SaferSignMessageRequestContainerView` to use `SignMessageRequestContentView` for details view display.

* Add explorer url button to tokens in `SaferSignTransactionView`

* Address review comment; always show receiving address in safer sign even when it's same as from address/account.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Do not cache user-initiated Refresh Status requests from the client
2 participants