<?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 Locate Button Issues with Google Chrome in Web AppBuilder Custom Widgets Questions</title>
    <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/locate-button-issues-with-google-chrome/m-p/854844#M11254</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone else had an issue with Google Chrome updating on Android and it rendering the locate button on multiple ArcGIS web apps completely useless?&amp;nbsp; I recently noticed it since my browser updated.&amp;nbsp; The maps were built with ArcGIS WebApp builder and all worked perfectly fine until this happened.&amp;nbsp; I've since went back to the factory version of Chrome and they started working again, but since they are being pushed out publicly I'd like to avoid this as a solution if it is possible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 May 2016 13:19:29 GMT</pubDate>
    <dc:creator>ChristopherHolewinski1</dc:creator>
    <dc:date>2016-05-03T13:19:29Z</dc:date>
    <item>
      <title>Locate Button Issues with Google Chrome</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/locate-button-issues-with-google-chrome/m-p/854844#M11254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Has anyone else had an issue with Google Chrome updating on Android and it rendering the locate button on multiple ArcGIS web apps completely useless?&amp;nbsp; I recently noticed it since my browser updated.&amp;nbsp; The maps were built with ArcGIS WebApp builder and all worked perfectly fine until this happened.&amp;nbsp; I've since went back to the factory version of Chrome and they started working again, but since they are being pushed out publicly I'd like to avoid this as a solution if it is possible.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 13:19:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/locate-button-issues-with-google-chrome/m-p/854844#M11254</guid>
      <dc:creator>ChristopherHolewinski1</dc:creator>
      <dc:date>2016-05-03T13:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: Locate Button Issues with Google Chrome</title>
      <link>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/locate-button-issues-with-google-chrome/m-p/854845#M11255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Chris,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; This is a complicated issue that Google has introduced in its later versions of Chrome. The issue is that they require https to be used for your app. Here is a blog about this issue from the JS API team (and WAB uses the JS API so it pertains to us as well).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://blogs.esri.com/esri/arcgis/2016/04/14/increased-web-api-security-in-google-chrome/" title="https://blogs.esri.com/esri/arcgis/2016/04/14/increased-web-api-security-in-google-chrome/"&gt;Increased web API security in Google Chrome | ArcGIS Blog&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 May 2016 13:35:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/web-appbuilder-custom-widgets-questions/locate-button-issues-with-google-chrome/m-p/854845#M11255</guid>
      <dc:creator>RobertScheitlin__GISP</dc:creator>
      <dc:date>2016-05-03T13:35:31Z</dc:date>
    </item>
  </channel>
</rss>

