<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic New CSP enhancements in Firefox 102 in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/new-csp-enhancements-in-firefox-102/m-p/8816#M3668</link>
    <description>&lt;P&gt;This is a WEBDEV question about the latest CSP enhancements in FF102:&lt;/P&gt;&lt;P&gt;"TransformStream and ReadableStream.pipeThrough have landed, allowing you to pipe from a ReadableStream to a WritableStream, executing a transformation on each chunk.&lt;/P&gt;&lt;P&gt;ReadableStream, TransformStream, and WritableStream are all transferable now.&lt;/P&gt;&lt;P&gt;Firefox now supports Content-Security-Policy (CSP) integration with WebAssembly. A document with a CSP that restricts scripts will no longer execute WebAssembly unless the policy uses 'unsafe-eval' or the new 'wasm-unsafe-eval' keyword."&lt;/P&gt;&lt;P&gt;QUESTION: Does this mean that web developers will have an easier, or more difficult job in coding sites with "better" CSP controls for working better in Firefox (say versus Chrome)?&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jun 2022 23:15:49 GMT</pubDate>
    <dc:creator>td47</dc:creator>
    <dc:date>2022-06-30T23:15:49Z</dc:date>
    <item>
      <title>New CSP enhancements in Firefox 102</title>
      <link>https://connect.mozilla.org/t5/discussions/new-csp-enhancements-in-firefox-102/m-p/8816#M3668</link>
      <description>&lt;P&gt;This is a WEBDEV question about the latest CSP enhancements in FF102:&lt;/P&gt;&lt;P&gt;"TransformStream and ReadableStream.pipeThrough have landed, allowing you to pipe from a ReadableStream to a WritableStream, executing a transformation on each chunk.&lt;/P&gt;&lt;P&gt;ReadableStream, TransformStream, and WritableStream are all transferable now.&lt;/P&gt;&lt;P&gt;Firefox now supports Content-Security-Policy (CSP) integration with WebAssembly. A document with a CSP that restricts scripts will no longer execute WebAssembly unless the policy uses 'unsafe-eval' or the new 'wasm-unsafe-eval' keyword."&lt;/P&gt;&lt;P&gt;QUESTION: Does this mean that web developers will have an easier, or more difficult job in coding sites with "better" CSP controls for working better in Firefox (say versus Chrome)?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2022 23:15:49 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/new-csp-enhancements-in-firefox-102/m-p/8816#M3668</guid>
      <dc:creator>td47</dc:creator>
      <dc:date>2022-06-30T23:15:49Z</dc:date>
    </item>
  </channel>
</rss>

