<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Permissions Policy on Nalar</title>
    <link>https://nalar.dev/tags/permissions-policy/</link>
    <description>Recent content in Permissions Policy on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/permissions-policy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Permissions Policy Bounds Browser Feature Authority</title>
      <link>https://nalar.dev/permissions-policy-bounds-browser-feature-authority/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/permissions-policy-bounds-browser-feature-authority/</guid>
      <description>&lt;h1 id=&#34;permissions-policy-bounds-browser-feature-authority&#34;&gt;Permissions Policy Bounds Browser Feature Authority&lt;/h1&gt;&#xA;&lt;p&gt;A page can embed code from several origins while still presenting a single application surface. That composition becomes security-relevant when browser capabilities such as geolocation, camera access, microphone access, fullscreen, or payment functions are available inside the resulting document tree. The code that renders a widget may not need the same browser authority as the application that hosts it.&lt;/p&gt;&#xA;&lt;p&gt;Permissions Policy gives a site a way to restrict selected web-platform features by origin and frame. It is not a replacement for user permission prompts, sandboxing, application authorization, or browser isolation. Its value is narrower and architectural: it can remove capabilities from documents that have no legitimate reason to exercise them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
