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 974
Fixed fresh install of Brave advertises Brave properties #7655
Labels
Milestone
Comments
Duplicate of #5892 cc: @bradleyrichter, @bbondy, @alexwykoff (in case we wanted to take action other than closing as a dupe) |
This is the worst (or best) example of this "bug" and we should block on it.
Of course this is a side effect of preloading top sites in the dashboard.
In this example, the search result suggestion should not be pre-filled but rather presented in the list and require a down arrow to access.
We may want to also create a new issue to mask out the preloaded top sites from the search suggestions so that this unintentional advertising is not perceived as intentional.
… On Mar 11, 2017, at 8:48 PM, Brian Clifton ***@***.***> wrote:
Duplicate of #5892
cc: @bradleyrichter, @bbondy, @alexwykoff (in case we wanted to take action other than closing as a dupe)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Seems like the user is asking for the preloaded Brave sites to not be in the urlbar suggestions at all |
@diracdeltas yup- we should be able to edit the site details to include a "leave me out of suggestions" flag. If the user then chooses to bookmark that site, we'd just want to clear that 😄 |
diracdeltas
added a commit
that referenced
this issue
Mar 14, 2017
fix #7655 Auditors: @bsclifton Test Plan: 1. open a clean instance of brave 2. type 'face' into the urlbar 3. it should autocomplete to facebook instead of Brave's facebook page
4 tasks
diracdeltas
added a commit
that referenced
this issue
Mar 14, 2017
fix #7655 Auditors: @bsclifton Test Plan: 1. open a clean instance of brave 2. type 'face' into the urlbar 3. it should autocomplete to facebook instead of Brave's facebook page
bsclifton
pushed a commit
that referenced
this issue
Mar 14, 2017
fix #7655 Auditors: @bsclifton Test Plan: 1. open a clean instance of brave 2. type 'face' into the urlbar 3. it should autocomplete to facebook instead of Brave's facebook page
bsclifton
pushed a commit
that referenced
this issue
Mar 14, 2017
fix #7655 Auditors: @bsclifton Test Plan: 1. open a clean instance of brave 2. type 'face' into the urlbar 3. it should autocomplete to facebook instead of Brave's facebook page
bsclifton
pushed a commit
that referenced
this issue
Mar 14, 2017
fix #7655 Auditors: @bsclifton Test Plan: 1. open a clean instance of brave 2. type 'face' into the urlbar 3. it should autocomplete to facebook instead of Brave's facebook page
This was referenced Mar 14, 2017
Reopening and removing milestone since the fix for this was reverted with e23e251 |
diracdeltas
added a commit
that referenced
this issue
Mar 16, 2017
fix #7655 Test Plan: 1. automated tests should pass 2. open clean instance of brave 3. type 'fa' into urlbar. you should not see brave's facebook page in the autosuggest. 4. go to about:history. there should be no brave sites.
4 tasks
This was referenced Mar 17, 2017
The branch was not updated, sorry for confusion! |
alexwykoff
changed the title
Fresh Install of Brave Advertises Brave Properties
Fixed fresh install of Brave advertises Brave properties
Mar 27, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test plan
#7753 (comment)
Did you search for similar issues before submitting this one?
Yes
Describe the issue you encountered:
A fresh install of Brave yields advertisements for Brave. This took at least one user by surprise when they tried the browser. Their feedback is available on Twitter:
Platform (Win7, 8, 10? macOS? Linux distro?):
All
Brave Version (revision SHA):
0.13.5
Steps to reproduce:
Actual result:
Brave advertises its own properties on a fresh install.
Expected result:
User expects no advertisements or promotion
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
Can this issue be consistently reproduced?
Yes
Extra QA steps:
#5594
The text was updated successfully, but these errors were encountered: