-
Notifications
You must be signed in to change notification settings - Fork 975
Constant nag popup asking "Ready to support your favorite sites?" #12758
Comments
I don't seem to have this issue. |
Interesting, I have Brave installed on 6 computers at home and work, and it does this on all six of them. |
cc: @bradleyrichter |
@NejcZdovc Can you post the current logic here so we can examine and adjust it accordingly? |
as far as I can tell from the notification this is triggered when we add promotion. We added disable option in 0.20 #12313 |
#12313 is only for BAT promotions. General Brave Payments invitations are separate. Those originally had a time restriction before first appearance. And a longer delay before appearance 2. I would like to use "no thanks" for the deny button on the second attempt which would disable further notifications until the user would opt-in to BP. |
yeah but if you check out initial issue |
Ah...yes. You are right. This mixed alert will be handled by the new switch for BAT offers. |
Can I make a suggestion to the devs? Rather than code ways to stop this message, you need to rethink some things. As in: don't do this in the first place. These types of messages are nothing but a nuisance and this type of behavior is what has driven the community away from other applications and websites. If someone wants to do something, they will. If they don't, then no amount of nagging is going to change that. It's simply going to make them leave, which I'm sure is not your intention. |
I would normally agree ^ but the current alert approach is working for UGP grant acceptance. We will improve Brave Payments awareness through better marketing and a better onboarding for new users. At that point we can reevaluate removal of nag alerts. To solve this nag for the majority, this is what we need to do: Show the first time at 10 days of browsing. On this 2nd nag, the button changes from “maybe later” to “no thanks” and never nags again. @NejcZdovc please reference this issue in the PR for this fix... |
Moving back to 0.22.x for now (since there isn't already a PR for this) |
Resolves brave#12758 Auditors: Test Plan:
@NejcZdovc @bradleyrichter confused on this one - per #12758 (comment) I get the sense (but it's not explicitly stated) that the 'No Thanks' button should not be displayed on the first appearance of this notification. However, per the test plan in #13465 I am seeing this 'No Thanks' button on the first appearance of the notification. Can one of you please clarify - should 'No Thanks' be displayed the first time or not? |
second question @NejcZdovc and @bradleyrichter - should the 'No Thanks' also be on this notification: |
@LaurenWags it should be on all promotion notifications |
@LaurenWags yes we should display it for the first time as well |
so then 'Maybe Later' does not change to 'No Thanks', correct? @NejcZdovc |
maybe later will show notification again in 24h, where no thanks will disable promotions @LaurenWags |
yes @LaurenWags - we didn't correctly update the test case. We decided to reduce NAG pain by giving the user more control on the first notice. Eventually the suggested choice on the far right will be an orange button as well. |
Thanks for the confirmations @NejcZdovc and @bradleyrichter! |
Verified on macOS 10.12.6 x64 using the following build:
Verified on Windows 7 x64
Went through verification on
|
Test Plan
#13465
Description
Brave browser displays unwanted nag screen, repeatedly.
Text: "Hello! Ready to support your favorite sites? Brave will fill your wallet with tokens to get you started!"
The only options are "maybe later" or "I'm ready". The "NO!" option is missing.
Steps to Reproduce
Actual result:
Expected result:
Reproduces how often:
Seems to occur every day on every installation of Brave.
Brave Version
about:brave info:
Brave: 0.19.139
rev: 99aa17d
Muon: 4.7.2
libchromiumcontent: 64.0.3282.85
V8: 6.4.388.20
Node.js: 7.9.0
Update Channel: Release
OS Platform: Microsoft Windows
OS Release: 10.0.16299
OS Architecture: x64
Reproducible on current live release:
Yes.
Additional Information
The text was updated successfully, but these errors were encountered: