1739442 - Add containerized mechanism to init documents with security information

Status: RESOLVED DUPLICATE of bug 1706026

(Core :: DOM: Security, task, P3)

Description

[Christoph Kerschbaumer [:ckerschb]]

Currently we are using patterns like the following when transferring security information or also initializing a new document.

aNewDoc->Reset(channel, loadGroup);
aNewDoc->SetPrincipals(sourcePrincipal, sourcePartitionedPrincipal);
aNewDoc->SetBaseURI(sourceDoc->GetDocBaseURI());
aNewDoc->SetSandboxFlags(sourceDoc->GetSandboxFlags());
aNewDoc->SetReferrerInfo(sourceDoc->GetReferrerInfo());
aNewDoc->SetEmbedderPolicy(sourceDoc->GetEmbedderPolicy());

Such patterns are obviously error prone and have caused problems quite so many teams. Ideally we are using some containerized mechanism when restting or initializing a document. Something like aNewDoc->SetSecurityInfo() or something there like, so in case we update one callsite the compiler would tell us all the other callsites and we can not accidentally forget to update one.