-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[113.0.5672.63 follow up] Fix build failure on master branch #30060
Comments
@brave/qa-team probably best to verify this once #30882 gets uplifted to |
@stephendonner #30882 came from another fix (brave/brave-core#17832). |
Verified
|
Brave | 1.53.83 Chromium: 114.0.5735.110 (Official Build) beta (64-bit) |
---|---|
Revision | 1c828682b85bbc70230a48f5e345489ec447373e-refs/branch-heads/5735_90@{#13} |
OS | Windows 10 Version 22H2 (Build 19045.3031) |
Steps:
- installed
1.53.83
- launched Brave
- opened
brave://settings/security
- confirmed default of
Standard protection
forSafe Browsing
- toggled it to
No protection (not recommended)
- loaded
https://www.majorgeeks.com/mg/get/fort_firewall,2.html
- waited
- confirmed auto-download
Save file as...
file picker was invoked - clicked
Save
- confirmed the downloads-bubble animation pointed to the downloads bubble
- clicked on the downloads bubble
- confirmed the file was marked as
Blocked - dangerous
- repeated the above, alternating
Discard
andKeep
scenarios
Confirmed I was prompted for and shown the downloads-bubble animation, regardless of the previous-download's blocked/unblocked status
Screencast:
Screenshots:
example | example | example | example | example | example | example | example |
---|---|---|---|---|---|---|---|
@mkarolin does this need to get checked on |
@kjozwiak I think we don't need to test this more on Android. it's desktop specific issue and above @stephendonner 's test result is sufficient. |
Thanks! I'll add |
Merge of brave/brave-core#18271 and brave/brave-core#18243 conflicted on master branch:
and more...
QA:
Please, verify that brave/brave-core#18243 still works.
The text was updated successfully, but these errors were encountered: