According to the current state of the document, using CPP might result in breaking some features when the user agent enforce the policy. But the feature might be critial.
example: my website promise is to load less than 800ko (resource-limit). If an heavy image is added, resulting in a violation of the directive, web browsers would block data after that the 800ko threshold has been reached. What if the block content is an essential JS or a CSS?
I think this behaviour would be a major issue.
Same goes for max-internal-blocking-size: I can't imagine how a browser could enforce the promise without resulting in major troubleshooting
Specifying a default Enforcement Policy for each directive would be great, and for some it would be usefull to override with a custom Enforcement Policy (eg: browser can only block images)
According to the current state of the document, using CPP might result in breaking some features when the user agent enforce the policy. But the feature might be critial.
example: my website promise is to load less than 800ko (
resource-limit). If an heavy image is added, resulting in a violation of the directive, web browsers would block data after that the 800ko threshold has been reached. What if the block content is an essential JS or a CSS? I think this behaviour would be a major issue.Same goes for
max-internal-blocking-size: I can't imagine how a browser could enforce the promise without resulting in major troubleshootingSpecifying a default Enforcement Policy for each directive would be great, and for some it would be usefull to override with a custom Enforcement Policy (eg: browser can only block images)