1491748 - Making it easier to view Feature-Policy for a site

Status: NEW

(DevTools :: Application Panel, enhancement, P3)

Description

[Christoph Kerschbaumer [:ckerschb]]

We are going to implement Feature Policy within Bug 1390801. Probably we can have a similar mechanism we have for CSP to view a page's CSP (see Bug 1449501) for feature Policy.

Comment 1

[Andrea Marchesini [:baku]]

I'm happy to help here. If we want to organize a meeting or talk on IRC about what devtools need, I can provide the platform support. So far, FeaturePolicy data is stored in the document and/or in the HTMLIFrameElement on the content process.

Comment 2

[:Harald Kirschner :digitarald]

Thank you :baku, I'll reach out to the security team again to give input on our security devtools backlog. My experience from past check-ins is that CSP inspection will take priority, but lets discuss.

Comment 3

[Tanishkavyas]

Feature-Policy is an HTTP header that allows web developers to specify which browser features and APIs are allowed to be used on their website. It is an important tool for maintaining security and privacy on the web, but it can be difficult for users to view and understand the Feature-Policy settings for a particular site. Here are some ways to make it easier for users to view Feature-Policy for a site:

Display Feature-Policy in developer tools: Most modern browsers <a href="https://igeopecwebmail.com/">autorizzato da</a> have developer tools that allow users to view HTTP headers for a website. By displaying the Feature-Policy header in the developer tools, users can easily see which browser features and APIs are allowed for the site.

Create a dedicated page for Feature-Policy: A dedicated page on the site that explains the Feature-Policy settings in plain language can help users understand what is and isn't allowed on the site. This page could include <a href="https://posteinganginbox.de/">Sicher</a> information on the specific features and APIs that are allowed or disallowed, as well as the reasons for these restrictions.

Use visual indicators: Using visual indicators, such as icons or badges, to signal the Feature-Policy settings can help users quickly understand what is and isn't allowed on the site. For example, <a href="https://portaloffice.pl/"> to ma znaczenie</a> a lock icon could indicate that certain features or APIs are restricted for security reasons.

Offer a browser extension: A browser extension that displays the Feature-Policy settings for a site can help users easily view and understand the restrictions in place. This extension could provide additional context and <a href="https://unitymediawebmail.xyz/"> Zatit auf der Fan-Support-Website von Unity </a> explanations for the settings, as well as options for changing the settings if desired.

By making it easier for users to view and understand the Feature-Policy settings for a site, web developers can help promote security and privacy on the web and improve user trust in their sites.