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 975
Added "Block All" cookie option in bravery panel #1987
Labels
Milestone
Comments
garvankeeley
changed the title
Cookie option in bravery panel missing "Block All"
Cookie option in bravery panel missing option "Block All"
May 30, 2016
Shipped |
I'm just seeing Accept every cookie and Block 3p cookies, not Block every cookie |
luixxiul
added
the
needs-info
Another team member needs information from the PR/issue opener.
label
Nov 16, 2016
Not shipped yet, as far as I can tell. |
cndouglas
removed
the
needs-info
Another team member needs information from the PR/issue opener.
label
Nov 16, 2016
My mistake. Read too fast. |
+1 on this, preferably for 1.0. I think this should be done in conjunction with #1268 such that cookies are blocked globally and there is a prompt to whitelist cookies on a page based on origin, because very few users want to block all cookies. |
For a first-pass I'll only add a setting to allow/deny all on a site |
diracdeltas
added a commit
to brave/sync
that referenced
this issue
Mar 15, 2017
diracdeltas
added a commit
that referenced
this issue
Mar 15, 2017
fix #1987 Test Plan: 1. automated cookies tests should pass 2. go to https://jsfiddle.net/7ke9r14a/9/ with default cookie settings 3. the page should show blank or "" for all result values 4. in the brave panel, set cookies to "Block all cookies" 5. the page should not load 6. now set cookies to Allow All 7. the page should display non-empty result values
luixxiul
added
QA/test-plan-specified
release-notes/include
and removed
enhancement
labels
Mar 15, 2017
This was referenced Mar 17, 2017
42 tasks
alexwykoff
changed the title
Cookie option in bravery panel missing option "Block All"
Added "Block All" cookie option in bravery panel
Mar 28, 2017
This was referenced Mar 28, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Test plan
#7721 (comment)
The text was updated successfully, but these errors were encountered: