Bug 152961
| Summary: | Content Blocker extensions: New load-type alternative: sibling-domains | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | me |
| Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | achristensen, benjamin |
| Priority: | P2 | ||
| Version: | Other | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
me
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".
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
me
Additionally a fourth "load-type" classification could be allowed for two domains -appropriately configured for https- that belong to the same entity, as seen in the security certificates.
This may be much more troublesome, though.