Open Bug 1530648 Opened 5 years ago Updated 2 years ago

[Feature Policy] Firefox only Web Platform Test failures

Categories

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

enhancement

Tracking

()

People

(Reporter: automatedtester, Unassigned)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [domsecurity-backlog1])

The following tests are failing in Firefox but passing in Chrome and Safari

/feature-policy/experimental-features/layout-animations-disabled-violation-report-js-tentative.html [1 subtests]
▶ /feature-policy/experimental-features/layout-animations-disabled-violation-report-keyframes-tentative.html [1 subtests]
▶ /feature-policy/payment-allowed-by-feature-policy-attribute-redirect-on-load.https.sub.html [2 subtests]
▶ /feature-policy/payment-allowed-by-feature-policy-attribute.https.sub.html [1 subtests]
▶ /feature-policy/payment-allowed-by-feature-policy.https.sub.html [3 subtests]
▶ /feature-policy/payment-default-feature-policy.https.sub.html [3 subtests]
▶ /feature-policy/reporting/document-write-report-only.html [1 subtests]
▶ /feature-policy/reporting/legacy-image-formats-reporting.html [1 subtests]
▶ /feature-policy/reporting/midi-report-only.html [1 subtests]
▶ /feature-policy/reporting/payment-report-only.https.html [1 subtests]
▶ /feature-policy/reporting/sync-xhr-report-only.html [1 subtests]
▶ /feature-policy/reporting/unoptimized-images-reporting.html [1 subtests]
▶ /feature-policy/reporting/unsized-media-reporting.html [1 subtests]

Source https://jgraham.github.io/wptdash/?bugComponent=core%3A%3Adom&tab=Firefox-only+Failures

Component: DOM → DOM: Security

Baku, is this something we should look into?

Flags: needinfo?(amarchesini)

/feature-policy/experimental-features/layout-animations-disabled-violation-report-js-tentative.html [1 subtests]
/feature-policy/experimental-features/layout-animations-disabled-violation-report-keyframes-tentative.html [1 subtests]

We don't have this feature implemented yet. Bug 1530994

/feature-policy/payment-allowed-by-feature-policy-attribute-redirect-on-load.https.sub.html [2 subtests]
/feature-policy/payment-allowed-by-feature-policy-attribute.https.sub.html [1 subtests]
/feature-policy/payment-allowed-by-feature-policy.https.sub.html [3 subtests]
/feature-policy/payment-default-feature-policy.https.sub.html [3 subtests]
/feature-policy/reporting/payment-report-only.https.html [1 subtests]

Marcos, do we care about this? Can yo ucheck why we are failing here?

▶ /feature-policy/reporting/document-write-report-only.html [1 subtests]
▶ /feature-policy/reporting/legacy-image-formats-reporting.html [1 subtests]
▶ /feature-policy/reporting/sync-xhr-report-only.html [1 subtests]
▶ /feature-policy/reporting/unoptimized-images-reporting.html [1 subtests]
▶ /feature-policy/reporting/unsized-media-reporting.html [1 subtests]

This are unsupported features yet. Annevk, you are following the feature-policy spec discussion. How urgent is the implementation of these features? Maybe we should wait until feature-policy is enabled by default before implementing these.

▶ /feature-policy/reporting/midi-report-only.html [1 subtests]

This should work. I'll check why it doesn't.

Flags: needinfo?(amarchesini) → needinfo?(mcaceres)
Flags: needinfo?(annevk)

See bug 1531012. I'd suggest we hold off for now until we have an agreed upon way forward.

Flags: needinfo?(annevk)

I'll check if what :foolip has sent makes a difference for the payments tests.

If not, happy to dive into those once we have some clarity from bug 1531012.

Flags: needinfo?(mcaceres)
Priority: -- → P3
Whiteboard: [domsecurity-backlog1]
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.