Policy container

[mozfreddyb]

Request for Mozilla Position on an Emerging Web Specification

• Specification Title: "policy container" in HTML
• Specification or proposal URL (if available): pull request that established it
• Explainer URL (if available): https://github.com/antosart/policy-container-explained
• Caniuse.com URL (optional): AFAIU this is not web exposed
• Bugzilla URL (optional): https://bugzilla.mozilla.org/show_bug.cgi?id=1706026
• Mozillians who can provide input (optional): @zcorpan or @tantek

Other information

[zcorpan]

If it's not web exposed, it doesn't need a standards position. Maybe there are some details that are exposed though, like the effects of inheritance. But I still think any such differences were spec bugs to begin with.

OK to close without a position?

[mozfreddyb]

I don't think this needs to be on the dashboard, but I wanted to make sure there are no objections. I take that to be true given the lack of opposition here.

[mozfreddyb]

I need to take that back. There are some web-visible changes that should come from implementing this.

In particular, there are some inheritance inconsistencies between browsers as highlighted by test cases in https://wpt.fyi/results/referrer-policy/generic/inheritance/iframe-inheritance-history-about-srcdoc.html?label=experimental&label=master&aligned

That being said, I think this is more of an argument in favor of doing this rather than anything else.

@zcorpan can you please confirm for posterity?

[zcorpan]

I think this applies for that test:

But I still think any such differences were spec bugs to begin with.

However, I think we don't have any objections here, so we can label as positive and not have a dashboard entry.