Security/Tracking protection/Default Cookie Restrictions/Bug triage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
# In order to reproduce, ensure the following prefs have the following values: | # In order to reproduce, ensure the following prefs have the following values: | ||
browser.contentblocking.enabled = true | |||
browser.fastblock.enabled = false | |||
privacy.trackingprotection.enabled = false | |||
network.cookie.cookieBehavior = 4 | |||
# Ensure the URL of the broken page is in the URL field | # Ensure the URL of the broken page is in the URL field | ||
# Close any unreproducible bugs with <tt>WORKSFORME</tt>. | # Close any unreproducible bugs with <tt>WORKSFORME</tt>. |
Latest revision as of 22:17, 19 September 2018
Bugs relating to the Default Cookie Restrictions feature should be triaged as follows.
- In order to reproduce, ensure the following prefs have the following values:
browser.contentblocking.enabled = true browser.fastblock.enabled = false privacy.trackingprotection.enabled = false network.cookie.cookieBehavior = 4
- Ensure the URL of the broken page is in the URL field
- Close any unreproducible bugs with WORKSFORME.
- Mark bugs that have the same root cause (e.g. Facebook login not working on site X) as DUPLICATE of one another.
- Paste what appears in the Web Console in a comment on the bug, or if it contains long URLs, attach it as a text attachment to the bug.
- If the bug is about a page breakage issue, make sure it blocks bug 1480137. Otherwise make sure it blocks bug 1473978.