Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Constant nag popup asking "Ready to support your favorite sites?" #12758

Closed
basildane opened this issue Jan 20, 2018 · 22 comments
Closed

Constant nag popup asking "Ready to support your favorite sites?" #12758

basildane opened this issue Jan 20, 2018 · 22 comments

Comments

@basildane
Copy link

basildane commented Jan 20, 2018

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

  1. Open Brave browser.
  2. Be annoyed.

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

@BraveSupporter
Copy link

I don't seem to have this issue.

@basildane
Copy link
Author

Interesting, I have Brave installed on 6 computers at home and work, and it does this on all six of them.

@bsclifton
Copy link
Member

cc: @bradleyrichter

@bradleyrichter
Copy link
Contributor

@NejcZdovc Can you post the current logic here so we can examine and adjust it accordingly?

@NejcZdovc
Copy link
Contributor

as far as I can tell from the notification this is triggered when we add promotion. We added disable option in 0.20 #12313

@bradleyrichter
Copy link
Contributor

#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.

@NejcZdovc
Copy link
Contributor

yeah but if you check out initial issue Brave will fill your wallet with tokens to get you started! it's about BAT promotion

@bradleyrichter
Copy link
Contributor

Ah...yes. You are right. This mixed alert will be handled by the new switch for BAT offers.

@srirambv
Copy link
Collaborator

@dfwdraco76
Copy link

dfwdraco76 commented Jan 28, 2018

My only options are "Maybe Later" and "I'm Ready". I've clicked "Maybe Later" at least a dozen times since installing beta 0.20.22 a day or two ago.

How can we make this stop?

capture

@basildane
Copy link
Author

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.

@bradleyrichter
Copy link
Contributor

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.
If answer is “maybe later”, then show again at 30 days.

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...

@bradleyrichter bradleyrichter added this to the 0.21.x (Beta Channel) milestone Feb 9, 2018
@bsclifton
Copy link
Member

Moving back to 0.22.x for now (since there isn't already a PR for this)

@bsclifton bsclifton modified the milestones: 0.21.x (Beta Channel), 0.22.x (Developer Channel) Feb 13, 2018
@bbondy bbondy modified the milestones: 0.22.x (Developer Channel), 0.23.x (Nightly Channel) Feb 25, 2018
@alexwykoff alexwykoff added the priority/P4 Minor loss of function. Workaround usually present. label Mar 13, 2018
NejcZdovc added a commit to NejcZdovc/browser-laptop that referenced this issue Mar 15, 2018
@NejcZdovc NejcZdovc modified the milestones: 0.23.x (Developer Channel), 0.22.x (Beta Channel) Mar 21, 2018
@LaurenWags
Copy link
Member

@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?

screen shot 2018-03-22 at 10 55 13 am

@LaurenWags
Copy link
Member

second question @NejcZdovc and @bradleyrichter - should the 'No Thanks' also be on this notification:

screen shot 2018-03-22 at 11 01 16 am

@NejcZdovc
Copy link
Contributor

@LaurenWags it should be on all promotion notifications

@NejcZdovc
Copy link
Contributor

@LaurenWags yes we should display it for the first time as well

@LaurenWags
Copy link
Member

so then 'Maybe Later' does not change to 'No Thanks', correct? @NejcZdovc

@NejcZdovc
Copy link
Contributor

maybe later will show notification again in 24h, where no thanks will disable promotions @LaurenWags

@bradleyrichter
Copy link
Contributor

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.

@LaurenWags
Copy link
Member

Thanks for the confirmations @NejcZdovc and @bradleyrichter!

@LaurenWags
Copy link
Member

LaurenWags commented Mar 23, 2018

Verified on macOS 10.12.6 x64 using the following build:

  • 0.22.7 8bb7e77
  • libchromiumcontent: 65.0.3325.181
  • muon: 5.1.1

Verified on Windows 7 x64

  • 0.22.7 8bb7e77
  • libchromiumcontent: 65.0.3325.181
  • muon: 5.1.1

Went through verification on Ubuntu 17.10.1 x64 using the following build:

  • 0.22.7 8bb7e77
  • libchromiumcontent: 65.0.3325.181
  • muon: 5.1.1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests