<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Content Blocker extensions: New load-type alternative: sibling-domains"
href="https://bugs.webkit.org/show_bug.cgi?id=152961">152961</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Content Blocker extensions: New load-type alternative: sibling-domains
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>Other
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>WebKit Misc.
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>me@josedante.com
</td>
</tr></table>
<p>
<div>
<pre>The current two alternatives available for load-type (third-party and first-party) are not enough.
It's common practice among websites, including many major ones. to use subdomains of their main domain to provide some of their content.
We should incorporate this practice into the content blockers spec.
A new load-type like "sibling-domains".</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>