<?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 An AudioContext was prevented from starting automatically. It must be created or resumed after a user gesture on the page. in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/an-audiocontext-was-prevented-from-starting-automatically-it/m-p/92324#M35895</link>
    <description>&lt;P&gt;hello everyone.&lt;/P&gt;&lt;P&gt;first of all, things that bug me, are incorrect statements and error's.&amp;nbsp; some may already have&amp;nbsp;expearienced this fault. and the browser can't seem to be seeing the difference between preload and user interaction.&amp;nbsp; it even claims to have the stopped the audiocontext it from running.&lt;/P&gt;&lt;P&gt;well, i see the point with user interaction, and the code runner should have noticed that&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;- it would stopped after preloading the context on it's own.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- secondly user interaction is masked through an event handler function.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- thirdly it wouldn't have started on it's own without user interaction.&lt;/P&gt;&lt;P&gt;so why is this warning given. since all code gets checked upon page load?&lt;/P&gt;</description>
    <pubDate>Fri, 04 Apr 2025 03:01:43 GMT</pubDate>
    <dc:creator>ko81</dc:creator>
    <dc:date>2025-04-04T03:01:43Z</dc:date>
    <item>
      <title>An AudioContext was prevented from starting automatically. It must be created or resumed after a user gesture on the page.</title>
      <link>https://connect.mozilla.org/t5/discussions/an-audiocontext-was-prevented-from-starting-automatically-it/m-p/92324#M35895</link>
      <description>&lt;P&gt;hello everyone.&lt;/P&gt;&lt;P&gt;first of all, things that bug me, are incorrect statements and error's.&amp;nbsp; some may already have&amp;nbsp;expearienced this fault. and the browser can't seem to be seeing the difference between preload and user interaction.&amp;nbsp; it even claims to have the stopped the audiocontext it from running.&lt;/P&gt;&lt;P&gt;well, i see the point with user interaction, and the code runner should have noticed that&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;- it would stopped after preloading the context on it's own.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- secondly user interaction is masked through an event handler function.&lt;/P&gt;&lt;P&gt;&amp;nbsp;- thirdly it wouldn't have started on it's own without user interaction.&lt;/P&gt;&lt;P&gt;so why is this warning given. since all code gets checked upon page load?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Apr 2025 03:01:43 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/an-audiocontext-was-prevented-from-starting-automatically-it/m-p/92324#M35895</guid>
      <dc:creator>ko81</dc:creator>
      <dc:date>2025-04-04T03:01:43Z</dc:date>
    </item>
  </channel>
</rss>

