This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 973
Verified publisher icon not shown on manual upgrade #10814
Labels
Comments
@srirambv does this issue still exist? |
luixxiul
added
the
needs-info
Another team member needs information from the PR/issue opener.
label
Sep 23, 2017
ghost
added this to the 0.19.x (Beta Channel) milestone
Sep 26, 2017
May be resolved by refactor #11037 . QA to recheck after |
luixxiul
removed
the
needs-info
Another team member needs information from the PR/issue opener.
label
Sep 26, 2017
Edit: The verified publisher icon shows up after a delay of ~10 secs on 0.19.20. Yet to verify on the older builds |
verified publisher icon is delayed, so it's ok if only appears after 10 sec |
closing for now as it works |
luixxiul
added
wontfix
invalid
and removed
bug
priority/P4
Minor loss of function. Workaround usually present.
wontfix
labels
Sep 29, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
Verified publisher icon not shown on manual upgrade
Platform (Win7, 8, 10? macOS? Linux distro?):
Windows 10 x64
Brave Version (revision SHA):
Steps to reproduce:
Actual result:
Verified publisher icon not shown on manual upgrade
Expected result:
Should show the verified publisher icon irrespective of when payment is enabled and how the browser update is done
Will the steps above reproduce in a fresh profile? If not what other info can be added?
Yes
Is this an issue in the currently released version?
Yes,
Updated manually from 0.17.13 to 0.18.14, no verified publisher icon shown
Auto updated from 0.18.14 to 0.18.23, still no verified publisher icon shown
Can this issue be consistently reproduced?
Yes
Extra QA steps:
1.
2.
3.
Screenshot if needed:
Any related issues:
cc: @mrose17 @NejcZdovc @cezaraugusto
The text was updated successfully, but these errors were encountered: