Confirmed users
908
edits
Security/Tracking protection/Bug triage: Difference between revisions
Security/Tracking protection/Bug triage (view source)
Revision as of 23:21, 21 June 2018
, 21 June 2018Use the URL field and mention the Disconnect categories
(Add the new tpimages and tplogin metabugs) |
(Use the URL field and mention the Disconnect categories) |
||
| Line 4: | Line 4: | ||
#* Platform bugs should be moved into '''Toolkit::Safe Browsing''' | #* Platform bugs should be moved into '''Toolkit::Safe Browsing''' | ||
#* Server-side bugs should be moved into '''Cloud Services::Server: Shavar''' | #* Server-side bugs should be moved into '''Cloud Services::Server: Shavar''' | ||
# Ensure the URL of the broken page is in the URL field | |||
# Breakage bugs should block one of these meta bugs: | # Breakage bugs should block one of these meta bugs: | ||
#* <tt>tppaywall</tt> if TP is triggering a paywall / adblocker detection script (e.g. [https://github.com/sitexw/FuckAdBlock FuckAdBlock]) | #* <tt>tppaywall</tt> if TP is triggering a paywall / adblocker detection script (e.g. [https://github.com/sitexw/FuckAdBlock FuckAdBlock]) | ||
| Line 30: | Line 31: | ||
# Close any unreproducible bugs with <tt>WORKSFORME</tt>. | # Close any unreproducible bugs with <tt>WORKSFORME</tt>. | ||
# Find the offending blocked resource and add a comment to the bug. | # Find the offending blocked resource and add a comment to the bug. | ||
# Tag bugs with the | # Tag bugs with the category that causes the breakage in the whiteboard field (use [https://github.com/mozilla-services/shavar-list-creation/blob/master/disconnect_mapping.py this mapping] for Twitter, Google and Facebook resources in the ''Disconnect'' category): | ||
#* '''tp- | #* '''tp-ads''' for the Advertising category | ||
#* '''tp-content''' for the strict list | #* '''tp-analytics''' for the Analytics category | ||
#* '''tp-social''' for the Social category | |||
#* '''tp-content''' for the Content category (only part of the strict list) | |||