Closed Bug 1535863 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 15792 - [ FeaturePolicy ] 'sandbox' vs 'allow' attributes

Categories

(Testing :: web-platform-tests, enhancement, P4)

Product:
Testing
Component:
web-platform-tests
Type:
enhancement

Tracking

(firefox68 fixed)

Status:
RESOLVED FIXED
Milestone:
mozilla68
Tracking Flags:
Tracking Status
firefox68 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 15792 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/15792
Details from upstream follow.

Ehsan Karamad <ekaramad@chromium.org> wrote:

[ FeaturePolicy ] 'sandbox' vs 'allow' attributes

This CL ensures that sandbox features set through 'allow' attribute take
precedence over the 'sandbox' attribute itsef. In line with this, any sandbox
flag which is converted to a container policy will be removed from the set of
flags for the corresponding frame owner. This ensures that the container policy
will not be overwritten by FrameOwner sandbox at the time of receiving the
feature policy headers.

The CL also packs a WPT which verifies the precedence of 'allow' over 'sandbox'.

Bug: 812381, 926293
Change-Id: Ic1d31dfb17ce4a81b5ead23b789119c04cfacd8d
Reviewed-on: https://chromium-review.googlesource.com/1508925
WPT-Export-Revision: 26c655437e034c5e59ff0944c50c78a313ffeacd

PR 15792 applied with additional changes from upstream: 9f49616e7fa90489fac85dd203e86d7c83ca67da
Failed to get results from try push
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/20eeca8c7d6b
[wpt PR 15792] - [ FeaturePolicy ] 'sandbox' vs 'allow' attributes, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/375f67a38d88
[wpt PR 15792] - [ FeaturePolicy ] 'sandbox' vs 'allow' attributes, a=testonly

https://hg.mozilla.org/mozilla-central/rev/20eeca8c7d6b
https://hg.mozilla.org/mozilla-central/rev/375f67a38d88

Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox68: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.