<?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 Re: Cannot use Stadia on Microsoft Edge in Stadia on Chrome</title>
    <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22708#M1391</link>
    <description>&lt;P&gt;This is infuriating, I could only get stadia to work on Edge. It seems to be a memory problem with my computer. But it ran well enough that I purchased Doom. Now that money is wasted and I haven't even beaten the game yet&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 17 May 2020 21:27:46 GMT</pubDate>
    <dc:creator>Postmortem</dc:creator>
    <dc:date>2020-05-17T21:27:46Z</dc:date>
    <item>
      <title>Cannot use Stadia on Microsoft Edge [FIXED]</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22537#M1365</link>
      <description>&lt;P&gt;Earlier this week I was playing on Edge just fine, but today I can't get past the Stadia logo. This can be bypassed by spoofing the User Agent in the developer console quite easily (F12 -&amp;gt; Top Right Menu -&amp;gt; More Tools -&amp;gt; Network Conditions), but this doesn't persist between sessions. I didn't update Edge recently, leading me to believe this is a Stadia issue. Can this be fixed?&lt;/P&gt;&lt;P&gt;EDIT: With no intervention of my own the issue has been fixed. Stadia can be used on Microsoft Edge again.&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2020 10:15:48 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22537#M1365</guid>
      <dc:creator>DryRoastedLemon</dc:creator>
      <dc:date>2020-05-19T10:15:48Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22547#M1367</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.stadia.com/t5/user/viewprofilepage/user-id/11258"&gt;@DryRoastedLemon&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;besides that the new Edge is build on Chromium,&amp;nbsp; just Google's Chrome browser is supported at the moment for playing Stadia. All others are workaround or "it could work but it is not offical".&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2020 14:20:33 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22547#M1367</guid>
      <dc:creator>Tobonaut</dc:creator>
      <dc:date>2020-05-15T14:20:33Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22556#M1370</link>
      <description>&lt;P&gt;Hi, understand that officially only Chrome is supported&amp;nbsp;&lt;STRONG&gt;but&amp;nbsp;&lt;/STRONG&gt;this is kind of a dirty trick:&lt;/P&gt;&lt;P&gt;- It was working perfectly fine since the other day&lt;/P&gt;&lt;P&gt;- It's a deliberate filter to ban other Chromium based browsers: it's not a technical problem or incompatibility since just spoofing the user-agent and "masquerading" as Chrome solves the issue&lt;/P&gt;&lt;P&gt;- It doesn't give any hint that the problem is an explicit ban of other browsers: it just fails silently making it seem that it's the alternative browser fault&lt;/P&gt;&lt;P&gt;I know I might face potential issues when using a chromium browser instead of Chrome and I can choose&amp;nbsp; but an outright and sudden block seems unjustified.&lt;/P&gt;&lt;P&gt;Davide&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2020 17:59:41 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22556#M1370</guid>
      <dc:creator>Apprendista</dc:creator>
      <dc:date>2020-05-15T17:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22558#M1371</link>
      <description>&lt;P&gt;I understand that Microsoft Edge isn’t officially supported, but it was working ever since Stadia was released. Not actively supporting a browser is something entirely different from locking a browser out, which is only understandable if it’s not Chromium based.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;So the question is not whether you can support Edge or any other Chromium browser, but if there’s a mistake causing Edge to be locked out&lt;/P&gt;</description>
      <pubDate>Fri, 15 May 2020 18:35:31 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22558#M1371</guid>
      <dc:creator>DryRoastedLemon</dc:creator>
      <dc:date>2020-05-15T18:35:31Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22597#M1375</link>
      <description>&lt;P&gt;Hi folks, just to keep it up.&lt;/P&gt;&lt;P&gt;I reported it to the team and they will have a close look. Let's cross fingers that you all will be able to play on Edge, soon again.&lt;/P&gt;</description>
      <pubDate>Sat, 16 May 2020 13:04:10 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22597#M1375</guid>
      <dc:creator>Tobonaut</dc:creator>
      <dc:date>2020-05-16T13:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22667#M1383</link>
      <description>&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;Perhaps this can be of help to the dev team. This is the console output when I load the site up. This is while I've disabled all the extensions that I'm using.&lt;/P&gt;&lt;P&gt;Side-note: I wanted to test this with in Incognito mode, but that throws the same errors and won't even allow me to log in. Clicking on the log-in button doesn't work.&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;home:1 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-B10sba4uUuKXXkt1AoUu+pvX0HYFq4wuii6uoCNcEqk='), or a nonce ('nonce-...') is required to enable inline execution.

home:1 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-M7m7Oi00iMmvAtOLXTWHqLiiFRTbAdt1b93GakL/smQ='), or a nonce ('nonce-...') is required to enable inline execution.

home:10 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-+npkL5kaN0hG/IfZ7QMwg7K1W7+9aVDCbOyc/v3COd4='), or a nonce ('nonce-...') is required to enable inline execution.

home:11 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-PQwEp1kqoFSZY0mRJEyNfM5eX4t6QU74uD1kQrbVJhI='), or a nonce ('nonce-...') is required to enable inline execution.

home:11 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-brmAynnJ26e6dQIgyzmfAML76+Z4ZD1pmWTr8+vLlcA='), or a nonce ('nonce-...') is required to enable inline execution.

9Refused to load the script '&amp;lt;URL&amp;gt;' because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' &amp;lt;URL&amp;gt; &amp;lt;URL&amp;gt; &amp;lt;URL&amp;gt; &amp;lt;URL&amp;gt; &amp;lt;URL&amp;gt; 'strict-dynamic' &amp;lt;URL&amp;gt; &amp;lt;URL&amp;gt; &amp;lt;URL&amp;gt; &amp;lt;URL&amp;gt;". 'strict-dynamic' is present, so host-based whitelisting is disabled. Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

home:61 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-+YT0g0YYKUqMiPGc46+QRZ607vYBRLK5y2p50SpGIdU='), or a nonce ('nonce-...') is required to enable inline execution.

home:61 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-Az+pePKiXlprpju9sHhn3XxpHR7pGiuvNuHVsWMAKgY='), or a nonce ('nonce-...') is required to enable inline execution.

home:61 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-A88IjvNPJUF2hmwAu3eoKeWJ+CrEq8bn52zBKZsHVLo='), or a nonce ('nonce-...') is required to enable inline execution.

home:73 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-w1HCKJswqtiC9T4tZdLXN4Vv83W9bRS2dlLmAqxe5Gc='), or a nonce ('nonce-...') is required to enable inline execution.

home:73 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-o5Ic+hnvlb5O6XnywHkSB23RZhMHORMYXNaSg+AjSi8='), or a nonce ('nonce-...') is required to enable inline execution.

home:73 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-NrpVwEaGIVOPEfk+GrH5MJH9iXN0nGthzyLKRUccJOI='), or a nonce ('nonce-...') is required to enable inline execution.

home:73 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-kHsdEBm93Wl8ujK5/E+hmWqxzybAUnCUkpk8NhWCI1E='), or a nonce ('nonce-...') is required to enable inline execution.

home:73 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-EbOZ4raByQfaWzRmUhd7ohVzEDylxip7+0AmHqhMxaw='), or a nonce ('nonce-...') is required to enable inline execution.

home:73 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-qayOoEA7CslAy2iIge6ltR9b6LPbKd6nJX1jhVhv/EI='), or a nonce ('nonce-...') is required to enable inline execution.

home:75 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-8QLOGlwkldA/43rkHgS4TBt7aKxo4F47w/8MNITjcZg='), or a nonce ('nonce-...') is required to enable inline execution.

home:78 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-enMO642Q7B5lj69HF4Qf+fuRhO/jItRdzrBmnBP1RKY='), or a nonce ('nonce-...') is required to enable inline execution.

home:79 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-VV4XvX96h/YdggtvawfHnIkwXk90e7yroq4+nrNEcHA='), or a nonce ('nonce-...') is required to enable inline execution.

home:83 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-IzO7x+FmEO0Qb5Zr+0po97W2M1vWFw+Lvshr9VNuF3I='), or a nonce ('nonce-...') is required to enable inline execution.

home:85 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-+JNq2jZSygJDXz1ov3EPav31vPtkopN85dHtNCOBm/w='), or a nonce ('nonce-...') is required to enable inline execution.

home:88 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-sw/maEekeWZYBHpuAQxZizvI89Ks59z7x1vDIerqwfA='), or a nonce ('nonce-...') is required to enable inline execution.

home:95 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-NCj4f70n95v0VHcqOARU3cTN1m+dw3mlC2zaF/k1bTc='), or a nonce ('nonce-...') is required to enable inline execution.

home:121 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-VNtNg0SBTl3/utjy57JVd9SlQMkEpXsUgqU3AGUXybg='), or a nonce ('nonce-...') is required to enable inline execution.

home:172 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-JuOjMt7YT1wIT5tkCfKHxLTKx3uKBV2qTtNdeAffOvQ='), or a nonce ('nonce-...') is required to enable inline execution.

home:996 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-VhiVoH8i575B1v9sEKJWOj57eSyVgm8m4w7hN80Q8pM='), or a nonce ('nonce-...') is required to enable inline execution.

home:29172 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-/Rb9cUp+zTv8E8qdPh2Zbi/pjyLCVYYZOMks2sUtS6U='), or a nonce ('nonce-...') is required to enable inline execution.

home:29172 Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'unsafe-inline' 'self' 'unsafe-eval' https://apis.google.com https://ssl.gstatic.com https://www.google.com https://www.gstatic.com https://www.google-analytics.com 'strict-dynamic' https://www.googletagmanager.com https://youtube.googleapis.com https://youtube.com https://s.ytimg.com". Either the 'unsafe-inline' keyword, a hash ('sha256-vV3n1DI8Aq0li5OykbNoqlot+0n4/xrdPeynP+atdqM='), or a nonce ('nonce-...') is required to enable inline execution.&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 17 May 2020 10:05:05 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22667#M1383</guid>
      <dc:creator>DryRoastedLemon</dc:creator>
      <dc:date>2020-05-17T10:05:05Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22708#M1391</link>
      <description>&lt;P&gt;This is infuriating, I could only get stadia to work on Edge. It seems to be a memory problem with my computer. But it ran well enough that I purchased Doom. Now that money is wasted and I haven't even beaten the game yet&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 17 May 2020 21:27:46 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22708#M1391</guid>
      <dc:creator>Postmortem</dc:creator>
      <dc:date>2020-05-17T21:27:46Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22783#M1395</link>
      <description>&lt;P&gt;&lt;a href="https://community.stadia.com/t5/user/viewprofilepage/user-id/19952"&gt;@Postmortem&lt;/a&gt;&amp;nbsp;What are you running on? If it works on Chromium Edge it should also work on any other Chromium derivate. Also, good news! It works again.&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2020 10:15:11 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22783#M1395</guid>
      <dc:creator>DryRoastedLemon</dc:creator>
      <dc:date>2020-05-19T10:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot use Stadia on Microsoft Edge</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22837#M1397</link>
      <description>&lt;P&gt;It is now working on Edge (Stable) but it has the issue both in the dev and canary versions: this may mean that the issue will simply resurface when Edge will be upgraded.&lt;/P&gt;&lt;P&gt;Spoofing User Agent to Chrome still solves the issue.&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2020 19:52:28 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Cannot-use-Stadia-on-Microsoft-Edge-FIXED/m-p/22837#M1397</guid>
      <dc:creator>Apprendista</dc:creator>
      <dc:date>2020-05-19T19:52:28Z</dc:date>
    </item>
  </channel>
</rss>

