<?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: Controller Inputs On Chrome Browser in Stadia on Chrome</title>
    <link>https://community.stadia.com/t5/Stadia-on-Chrome/Controller-Inputs-On-Chrome-Browser/m-p/13774#M709</link>
    <description>&lt;P&gt;&lt;a href="https://community.stadia.com/t5/user/viewprofilepage/user-id/10766"&gt;@CookieMcCrumble&lt;/a&gt;&amp;nbsp;: Same behavior for me too.&amp;nbsp; I believe that that is just the way that it is implemented currently.&amp;nbsp; Hopefully they'll get around to addressing it as a silent feature in due course.&lt;/P&gt;</description>
    <pubDate>Sat, 25 Jan 2020 15:11:24 GMT</pubDate>
    <dc:creator>Mad_Dog_Bravo</dc:creator>
    <dc:date>2020-01-25T15:11:24Z</dc:date>
    <item>
      <title>Controller Inputs On Chrome Browser</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Controller-Inputs-On-Chrome-Browser/m-p/13768#M708</link>
      <description>&lt;P&gt;No problems at all running Stadia through the chrome browser here, performance wise it's absolutely fine.&lt;/P&gt;&lt;P&gt;My only complaint, is the controller support in the browser itself before launching a game. I can toggle through games fine, even select one, but that last click that's required to sometimes load the game (when the big red play button comes up) wont activate without a mouse press.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure if it's something my end that someone has a quick and easy "you're a pleb, this is what you do!", or if it's something known.&lt;/P&gt;&lt;P&gt;Hopefully a fix isn't far off!&lt;/P&gt;</description>
      <pubDate>Sat, 25 Jan 2020 13:32:38 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Controller-Inputs-On-Chrome-Browser/m-p/13768#M708</guid>
      <dc:creator>CookieMcCrumble</dc:creator>
      <dc:date>2020-01-25T13:32:38Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Inputs On Chrome Browser</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Controller-Inputs-On-Chrome-Browser/m-p/13774#M709</link>
      <description>&lt;P&gt;&lt;a href="https://community.stadia.com/t5/user/viewprofilepage/user-id/10766"&gt;@CookieMcCrumble&lt;/a&gt;&amp;nbsp;: Same behavior for me too.&amp;nbsp; I believe that that is just the way that it is implemented currently.&amp;nbsp; Hopefully they'll get around to addressing it as a silent feature in due course.&lt;/P&gt;</description>
      <pubDate>Sat, 25 Jan 2020 15:11:24 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Controller-Inputs-On-Chrome-Browser/m-p/13774#M709</guid>
      <dc:creator>Mad_Dog_Bravo</dc:creator>
      <dc:date>2020-01-25T15:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Inputs On Chrome Browser</title>
      <link>https://community.stadia.com/t5/Stadia-on-Chrome/Controller-Inputs-On-Chrome-Browser/m-p/13904#M711</link>
      <description>&lt;P&gt;&lt;a href="https://community.stadia.com/t5/user/viewprofilepage/user-id/10766"&gt;@CookieMcCrumble&lt;/a&gt;&amp;nbsp;It's definitely not just you. It happens to me every time whenever I start Destiny 2 while playing with controller. Make sure to submit feedback through the Stadia app. The more people sending feedback about the issue, the better chance it's getting fixed sooner.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jan 2020 14:35:17 GMT</pubDate>
      <guid>https://community.stadia.com/t5/Stadia-on-Chrome/Controller-Inputs-On-Chrome-Browser/m-p/13904#M711</guid>
      <dc:creator>Ivan</dc:creator>
      <dc:date>2020-01-27T14:35:17Z</dc:date>
    </item>
  </channel>
</rss>

